In regards to your point, using other backends other than LLVM and cargo having full support for binary libraries would solve a big part of the compilation time story.
In spite of its fame, C++ builds can be made relatively fast when using binary libraries, and even on its baby state, one can already notice some difference with modules workloads in Visual C++.
So I am still hopeful that Rust will improve its compilation story.
I've never seen this in the wild and to be honest, it seems massively inconvenient to write a library, create a C-compatible interface for it (meaning you lose out on most benefits of Rust's type system), and then write a wrapper for said C-like API to regain type/memory safety and abstraction power. The killer is that you lose the ability to use traits in the interface between, which idiomatic Rust heavily relies upon.
Those stability practices is what allows me to use Qt, VCL, MFC, .... without rebuilding the world every time I need to start something new with them.
It also allows several companies to sell C and C++ libraries, that wouldn't have done otherwise.