If the debugger could let you step one event or condition/action at a time and be able to inspect what is being picked then that would probably satisfy the op. Also would it be possible to set break points in triggered events and let you step through that?
Currently debugging events is something new users have trouble with. More advanced users resort to logging text or visualizing what's picked somehow manually. Debugging more complex events usually requires disabling most of the events and building it up a little at a time while visualizing what's picked. In some cases advanced users can mentally run through the events as they read it to find what's amiss but in most cases it's easier to scrap it and start from scratch.
Anyways being able to debug events at a finer level would be useful in helping new users with the nuances of the event system and advanced users to identify where their events are failing.