> And since Rust code can largely if not totally avoid such problems when properly implemented, memory safety now looks a lot like a national security issue.
When properly implemented. That's the whole issue, isn't it? After all, the same can be said for C++, too.
I'm not a Rust expert by any means, but I'm familiar enough with its memory protection mechanisms to know that competent C++ teams have established conventions providing the same memory safety. The advantage Rust has is you don't have to rely on convention, which makes it easier to use 3rd party libraries. On the flip side, C++ teams tend to not use a plethora of 3rd party libraries and the ones they do use tend to be extensively used and well-known.
What I'd like to see is a non-trivial problem system specification provided to an experienced Rust team and an experienced C++ team and see which team is faster. Wouldn't surprise me if the Rust team were more productive, but it also wouldn't surprise me if they weren't anywhere near close to being twice as productive.