> You can not stop the users from shooting themselves in the foot, but that is not the goal here.

It should be the goal. Even experts make mistakes. This is why static type systems exist. The logical thing to do is to strengthen the type system to prevent more classes of errors.

And yet you always need to provide users an way out for the sake of pragmatism. Examples: Rust's unsafe block, Haskell's Unsafe.Coerce, etc.

If the user avoids the analogous features in C++ and stick to modern conventions, it is not less safe/secure.