I skimmed the video, putting a loop inside an autorun event is kinda redundant. Autoruns already loop. Player input is already halted during event processing (unless it's a parallel process). Also you never want any kind of loop without a wait of some kind. So my advice would be to change the trigger (the autorun) on the first common event to none. Then just under the loop command and before anything else, do a wait:1 and see if that stops your freezing problem.
Hope this helps and good luck!
H̶e̶y̶a̶!̶ ̶T̶h̶a̶n̶k̶s̶ ̶a̶ ̶l̶o̶t̶ ̶f̶o̶r̶ ̶t̶a̶k̶i̶n̶g̶ ̶a̶ ̶l̶o̶o̶k̶ ̶a̶n̶d̶ ̶p̶i̶t̶c̶h̶i̶n̶g̶ ̶i̶n̶,̶ ̶s̶a̶d̶l̶y̶ ̶I̶ ̶c̶a̶n̶ ̶c̶o̶n̶f̶i̶r̶m̶ ̶t̶h̶a̶t̶ ̶a̶f̶t̶e̶r̶ ̶d̶o̶i̶n̶g̶ ̶l̶i̶k̶e̶ ̶y̶o̶u̶ ̶s̶a̶i̶d̶,̶ ̶e̶x̶c̶h̶a̶n̶g̶i̶n̶g̶ ̶a̶l̶l̶ ̶t̶h̶e̶ ̶S̶w̶i̶t̶c̶h̶ ̶c̶a̶l̶l̶s̶ ̶t̶o̶ ̶e̶n̶a̶b̶l̶e̶ ̶t̶h̶e̶ ̶A̶u̶t̶o̶r̶u̶n̶ ̶c̶o̶m̶m̶o̶n̶ ̶e̶v̶e̶n̶t̶ ̶w̶i̶t̶h̶ ̶c̶a̶l̶l̶s̶ ̶t̶o̶ ̶t̶h̶e̶ ̶n̶o̶w̶ ̶"̶r̶e̶g̶u̶l̶a̶r̶"̶ ̶c̶o̶m̶m̶o̶n̶ ̶e̶v̶e̶n̶t̶ ̶a̶n̶d̶ ̶i̶n̶c̶l̶u̶d̶i̶n̶g̶ ̶e̶x̶t̶r̶a̶ ̶W̶a̶i̶t̶:̶1̶ ̶(̶w̶h̶i̶c̶h̶ ̶h̶a̶s̶ ̶s̶o̶l̶v̶e̶d̶ ̶a̶ ̶m̶y̶r̶i̶a̶d̶ ̶o̶f̶ ̶p̶r̶o̶b̶l̶e̶m̶s̶ ̶f̶o̶r̶ ̶m̶e̶ ̶i̶n̶ ̶t̶h̶e̶ ̶p̶a̶s̶t̶ ̶a̶s̶ ̶w̶e̶l̶l̶)̶ ̶t̶h̶e̶ ̶m̶i̶n̶i̶g̶a̶m̶e̶ ̶s̶t̶i̶l̶l̶ ̶b̶e̶h̶a̶v̶e̶s̶ ̶i̶n̶ ̶t̶h̶e̶ ̶e̶x̶a̶c̶t̶ ̶s̶a̶m̶e̶ ̶w̶a̶y̶,̶ ̶3̶0̶f̶p̶s̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶t̶h̶e̶ ̶H̶i̶g̶h̶_̶H̶z̶_̶F̶i̶x̶ ̶a̶n̶d̶ ̶0̶-̶5̶f̶p̶s̶ ̶w̶i̶t̶h̶ ̶i̶t̶ ̶t̶u̶r̶n̶e̶d̶ ̶o̶n̶.̶ (seems I made a silly user error when I saved a backup of the common events in neglecting to remove the autorun from the backup..heh..)
First off I want to apologize for apparently unnecessarily derailing this thread, because in the end it was entirely resolvable on an Event-Level like TheAM-Dol originally stated to assume.
This was actually the first time I have went so deep into the eventing for RPG Maker as I've always been able to find a polished solution to anything in the form of a plugin somewhere within this awesome community, and I have learned a whole lot from it.
After tinkering with the common events quite a bit as advised by Slaughty, for some strange reason reversing a process here and there to solve weird things that happened once it stopped relying on the Autorun and learning how to properly utilize Labels within the main common event instead of having it as an Autorun to begin with, it's now fully functional "as intended" at 60fps.
Once again I'm sorry for this turning out to be a completely off-topic "me problem" I should have just opened a seperate thread.
:rheh:
Perhaps one relevant useful take from all of this is that punishing the user for terrible use of autorun events could be considered yet another great feature of Mac's magnificent plugin solution.