On the other hand, "a new kid in town" is not a good reason to declare a rewrite a failure. Did it make your life better? Did it reduce bugs with a reasonable amount of effort? Maybe it was a good decision after all, given what you knew and what was available at the time.
Meanwhile, delaying a decision indefinitely just in case better options appear later is probably a road to death. Again, Rust doesn't come into the question all that strongly.
There's a lot of overhead that can't really be reduced.
This is nothing new ...
See: the mid-to-late 1990s and Perl, Python, Tcl, etc.
The only way to predict the furture is to create it.
You could see the seeds of Rust from years ago, but having a nice language as the start is just... the start.
Rust do that AND all the other things: tooling and docs and..
So, the thing that will replace Rust will need that, and is likely you will not see any proper* contender in the next 5 years, maybe even more...
*ie: One where it worth to rewrite the codebase. You will see several experiments, maybe a few very good, but consider this: To rewrite from C/C++/.. to Rust have a lot of leverage: C performance, superior tooling, superior error messages, superior docs. Your Rust replacement should be BETTER than that.