For me, it looks better once there's also the get section, but I can remove this, not a problem.

Rust complains:

pointer argument requires that the function be marked unsafe

I assume we have to mark these functions unsafe. I don't fully understand your concern, they're about to be called from c++ exclusively and I didn't notice any impact of unsafe on how we call them in c++ really. And I don't think we'll want to use them from rust.

Ok, that surprising. I thought that only dereferencing a raw pointer is unsafe.
https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html#unsafe-superpowers
So maybe what happens here is that Rust automatically dereferences a raw pointer when it is a function argument...

I don't fully understand your concern, they're about to be called from c++ exclusively and I didn't notice any impact of unsafe on how we call them in c++ really.

The issue is not on C++ side but on the Rust one. If we mark the function as unsafe, we can use unsafe operations in the whole function. According to the book:

People are fallible, and mistakes will happen, but by requiring these five unsafe operations to be inside blocks annotated with unsafe you’ll know that any errors related to memory safety must be within an unsafe block. Keep unsafe blocks small; you’ll be thankful later when you investigate memory bugs.

It is a good practice to keep unsafe blocks as small as possible.

Discussed offline. I understand that it's better to make unsafe areas as small as possible but here we have no choice, I'm afraid.