Sorry I just realized that I never followed up. So that added tick box actually solved part of my problem and I was able to create a workaround to solve the remainder and I feel like I should explain in case any of it is helpful.To add (I hate the edit limits here), the 1st workaround is good for quick hotkey presses etc. that need to be considered ASAP and if your actions are sorted in a way that results in stopping the not too important parts.
Queues workaround works well for things that can go slower, like showing new Twitch subscribers in possibly infinitely long separate popups.
Shorter checks work only if the 1st workaround isn't required due to ongoing long actions and will use more CPU as all conditions will execute with higher frequency. Maybe some day separate timers for each macro would be great, I think it wouldn't be too easy to implement, though.
The main functionality I was shooting for was to be able to read midi input with this plugin and communicate (via hotkey macros for now) to a piece of software I use (SAMMI) that cannot read midi data so I can perform some other logic.
I found that the plugin takes in all midi data without any loss that I personally found but my macro was not activating as frequent as I needed it. I'm guessing this is from the limit on how frequent macros can be checked (mine is set to 10ms) which is fair though I was losing out on this midi macro firing if the midi data came in too quick in succession.
So the work around I made was to make two counter variables, one in advanced scene switcher and one in SAMMI then checking to see if there's a mismatch and then handling it if so.
It's a little wonky but it works!
Edit: typos