Typically, No.
Once you start "speedwalking", any new commands are added to the end of the speedwalk stack. Even a scripted "send" will append the text to the end of the speedwalk.
I have witnessed triggers fire while I am speedwalking, but the text they have commanded be sent to the mud do not get sent until the speedwalk is delayed.
You could, of course, write your own script to workaround this. You script would prabably parse a string of multiple commands, and send each one after a timer had fired.
Sub MySpeedWalk
'build an array with the list of commands to send to the mud.
'make a MySpeedWalkTimer to fire after a delay.
Sub OnMySpeedWalk '<- Called by the timer.
'Send the next command.
'Is there another command to be sent?
'Yes? Make another MySpeedWalkTimer.
'No? Do nothing
That's the basic psuedocode... You could then build "flags" into it, to shut off when an event (trigger) occurs. You might check for the flag before "Send the next command", and abort if need be.
The downside to this is you can only make timers with a whole number of seconds, so you can't set the delay to a fraction of a second... Almost anything is possible via scripting, so you may even be able to work around that. :)