> Correct use, documentation, and other concerns are important for all libraries, whether got via cargo or otherwise
This is true.
However the Cargo/Rust ecosystem has one standard answer, read the associated crate docs, e.g.:
Coincidentally, the above linked crate `libloading` also shows how to access functionality in a shared library that exposes a C ABI compatible interface whatever the implementation language.
More importantly, though: how hard is it to use a library coded in C++ from your Rust program? You have to make and maintain some sort of shim layer. Even a C library needs some such effort. For any given need, you are much less likely to find an existing and suitable Rust library already written, released, and maintained than one in some other, more widely used, language.