To me Rust is a suboptimal choice for lot of other use cases.
Automatic memory management should be embraced 90% of the time, but it is not due to cargo-cult (no pun intended, Rust's cargo is awesome) and superstition. I mean, people successfully did "systems programming" in GCed languages decades ago. They were lucky nobody told them that is not achievable.
Besides Python that I have to use professionally for its numpys and matplotlibs, personally I settled on Go for my personal purposes, with all its warts and caveman-like design, even though I prefer a lot of Rust stuff (error handling, type system, FP-like constructs). D or C# came pretty close, as languages alone they are much better than Go, but tooling and ecosystem, in case of D, or still somewhat limited AOT capabilities, in case of C#, made Go a winner for me.
While I am not a big fan of Go's design decisions, I am a cheerleader for TinyGo and TamaGo achievements, or having bootstraped the whole compiler toolchain and runtime.
Likewise, even though I dislike the outcome from Android Java, I celebrate that Android has proven what Longhorn could have been if DevDiv and Windows division actually collaborated.
Also share the same opinion regarding Rust, its sweetspot are places where any kind of automatic resource management isn't wanted, or even if possible, it would be quixotic battle trying to change the minds of the target audience.
Besides Python that I have to use professionally for its numpys and matplotlibs, personally I settled on Go for my personal purposes, with all its warts and caveman-like design, even though I prefer a lot of Rust stuff (error handling, type system, FP-like constructs). D or C# came pretty close, as languages alone they are much better than Go, but tooling and ecosystem, in case of D, or still somewhat limited AOT capabilities, in case of C#, made Go a winner for me.