I'm not sure I understand your problem then. The scenario I had running (and I checked before posting) was:
Event A to run 5 seconds after every other event (the timeout - I kept it simple)
Event B was triggered from a button on the front panel
Press Button - Event B triggered
Wait 2 seconds
Press Button - Event B triggered
Wait 6 seconds
After 5 seconds - Event A triggered
Had I wanted to ensure that event A hadn't been reset then I would have some time maintenance going as well, with a couple of shift registers, or a functional global.
If what you want is to trigger event A early, then just queue it early, and manage the queue. Don't forget there is a flush queue VI which will just empty the queue of all data which is what I use whenever I need to quit a producer/consumer set of loops - producer flushes queue then enques quit element - all that is then in the queue is the quit, and no errors. I probably assumed a producer consumer, or a looped state machine which runs continuoulsy with a stop only occurring in one specific situation, which means that a dequeue will only timeout when it has not had any other element populated within that time.