The problem as i see it is that as mirc is single tasked within its scripting enviroment etc, so to get access to do the simulated events mirc must have idled to allow you to have typed it in, if they were in some form of script, then mirc would need to buffer them all tell that script ended then process them all like regular events. The only way i can see you getting anything out of it besides the most basic of script debugging checks is to set of a huge set of timers of simulated events to emulate the interaction from a server.

I would suggest you maybe just write your events in a mode what you can simulate them being run in
ie: someone typing "!event etc etc etc" in a channel can be written like this.
Code:
on *:text:!event *:#: { on.text.!event $chan $nick $1- }
alias on.text.!event {
  var %chan = $1
  var %nick = $2
  tokenize 32 $3-
  ; ^ U can add as many other $identifiers that are event specific as you need and then tokenize 32 the remaining $1- parameters
  ;
  ... other code using %chan and %nick etc in replace of $chan and $nick etc ...
}


Then to simulate it you just write /on.text.!event channel nick !event blah blah blah