We can't say that (yet) about Swift and Rust. In 3-5 years I think this is going to be a very different conversation, though.
In my mind, C++'s flexibility is both its greatest benefit and its greatest danger. You can do almost anything, and there are so many ways to do it. I agree this is a "problem" that's likely not going to be fixed. You can ask your fellow developers to read Scott Meyer's Effective (Modern) C++, you can go to meetups, listen to the wisdom of the steering committee, etc. but at the end of the day it really boils down to the fact that your team needs to be committed to being resilient and responsible. That's true in any language, but much more so in C++.
Not sure about Swift, I haven't really been paying attention in that space.
Writing proper code in C++ requires, as you say, "your team needs to be committed to being resilient and responsible", which just doesn't happen on my little piece of the world.
So using it in personal projects, yeah. At work, not really.
Even then, in C++ you still need to expose a C interface, so it feels at least on even footing with Rust. But of course, I am biased...