I think this dual-input technique should be encouraged. It opens up new strategies and potential shortcuts, which is great for the community. To accommodate it fairly, we should probably create a specific category for runs using it, alongside the existing ones.

My suggestion is to define two main categories:

Glitchless: No intentional exploits, bugs, or glitches allowed (including this dual-input method, timer resets, checkpoint orb resets, hidden timer glitches, or clipping on respawn). Timing uses the real time for accuracy.

Any%: Allows all in game techniques without modifying games – including timer resets, this dual-input boost, checkpoint orb resets, hidden timer glitches, and clipping on respawn objects. Timing uses the displayed timer (acknowledging its known quirks, like the milliseconds rolling over from .99 to .00, which can sometimes cause minor timing discrepancies).

This structure keeps glitchless runs pure while giving a dedicated space for runs utilizing this cool find and other exploits.

btw, some of my own runs that manipulate the timer would also need to be reclassified into Any% under this system.