For me i think the execution limit is there for a reason, well from this old post i found
It’s there to stop infinite loops and to make the simulations bound(?) (i think to make sure that each player runs only one while loop iteration per frame, so no code reacts faster than the other, basically waiting for the other player to finish the current frame’s while loop)
I have a few ideas on this:
-Increase the execution limit specifically for top matches in tournaments(don’t really recommend this)
or
-Show how many statements are the limit untill that error is shown, and show how many statement executions are executed for the player so far (if possible update them every frame, however if not just show how many statements the player’s code executed at the end of the match so they can optimize)
Coding sometimes is not only about figuring out the logic, but to optimize the logic so your code can complete it faster, opening up rooms for more calculations.