When you make a mistake with ASM the result is game crash if you hack the right location. So a crash is half the way to success as you have found something relevant.
Since the byte order of your code is wrong, what it tells you is those function were never called.
One obstacle to ASM hacking is those code that just sit there and do nothing. Sometimes you can see from the function name that those code are for PC.
Many years ago I asked a software engineer to flip a bit of a certain register and he told me he can't, I don't accept that so I looked into the code, what I saw was a horror show, it is impossible to go through the code as a unaided human as the code base had all the previous generations and variants of the product in there! ( bloody cheat on code reuse KPI is what I think it was )