The only difference between C++ and "immutable by design" languages is that in C++ you'd have to write your own little processor to ensure that your rule is followed (this is no big deal, and I've written much more complex processors to enforce C++ coding standards as part of the build.)
What do you mean by unexpected order? I find event driven code to be the easiest to understand and maintain. Typically, you will be forced to specify order explicitly, i.e. nesting callbacks for sequential execution or not for parallel.
Events are find if your app is stateless (boring). Otherwise you may get events when things are not ready for them. You can get around that with lots of checking, or perhaps building a nice OO system underneath may help. I have a hard time explaining this because it can be subtle. See the Therac 25 for an example.
I've got this renderer that takes a huge data structure and uses simple OpenMP constructs to draw images. There is an assumption that the underlying data will not change during a render. Do I need a functional language to enforce this? No. Would it be nice if C++ had a feature to enforce it? Yes. Will I eventually want to make something that can carefully modify the data while rendering? Maybe, but I'm not sure that even makes sense.
I think a bigger threat is event driven code which IMHO is notorious for making things happen in unexpected order.