Don't be so quick to judge. I didn't look at the code but what I heard is that Arisu (mod creator) saved CPU cycles by using a compiler that executes out-of-order instructions.
I didn't use any compiler at all. It all was hand-written. Compilers can't execute out-of-order, compilers only can generate code which CPUs can execute. The generated code can be and always is executed out-of-order as fast as possible, so the CPU execution modelling has been one of the standard optimizations for any compiler, including the GNU C Compiler (may be known as --march to some), for ages.
If this is true, then don't blame the programmers: They were doing it by the books. In-order instructions are considered safe, even if they eat cycles. Out-of-order instructions are not safe, since you might need to change a variable later that you are trying to change out of order.
Sorry, but that isn't true. What the compiler generates hasn't directly to do with what the programmers wrote, except that it retains the semantics. Out-of-order execution is not unsafe, it's actually something different than what you mean. What you are describing here is deliberate elimination of mutexes or other synchronization primitives. Yes, that'd be unsafe, but nothing of this kind has been done and can easily be verified by looking at the source code.
Edit: If you wish to read more about OoOE as it is commonly understood, https://en.wikipedia.org/wiki/Out-of-order_execution might be a good place to start.