Having properties like immutability and pureness in your language makes it lot easier to trust your code and to reason about it.
Please, read exactly.
"... unless you're working in Haskell and even there you could find ways to screw things up by interacting with the outside world, which isn't immutable."
The whole point is, that you're able to express immutability and pureness in a language like Haskell _AND_ have a compiler which can verify it.
You will never be able to prohibit any screwing, but you can make it a lot harder to screw something.
X = 5.
X2 = X+1.
C++: const int x = 5;
const int x2 = x + 1.
My C++ style use const modifiers extensively.
Likewise you can use final in Java.const_cast isn't the big issue, because there's also unsafePerformIO in Haskell. For both you could say, that they shouldn't be used, that it's bad programming practice to use them.
The point is, even if you follow good programming practices in C++, you can't express them and your compiler can't help you in the verification, if you're really following them.
That doesn't might seem like a big thing, it's also not related to your smartness, because it mostly depends on the size and complexity of your system.