Keeping planes from crashing and bank accounts correct matter too. Rust solves a subset of memory safety problems but it is not a programming language for high assurance applications and in that context enables many other types of unsafe behavior.
Most systems programming languages don't make it simple and many people don't do it but it is definitely valuable and worth doing when the economics make sense.
Even with a fully verified toolchain there will still be bugs. I once had a customer find a rare bug in a database engine that was ultimately caused by slight differences in behavior between microarchitectures running the same binary.
Tautologically so.
"Which of the following tools do you or your team use for guideline enforcement or other code quality/analysis?"
https://www.cvedetails.com/top-50-vendors.php
Microsoft 6508/116769 = 5.5%
Apple 4502/116769 = 3.8%
Google 4110/116769 = 3.5%
total (6508 + 4502 + 4110)/116769 = 13%
Have you looked at the CVE stats of the last decade recently? Memory errors make up around 3/4 of that. Even if Rust would make the last quartile harder (which in my experience it doesn't), it could still be worth it for many applications where you cannot afford full verification, but want to avoid your users being pwned.