I have often thought that 215 was inclusive of whatever event caused spid to wait.....so, if you had 200 for 29 (WaitTime) and it had to wait 100ms for CPU, 215 would show 300ms. At least all the data I have looked at in the past seems to indicate this is true (or else we have a lot of really slow scheduling out there).
It would be interesting to see the raw monProcessObject & monProcessStatement at same times of monProcessWaits - if you are taking a long time to read the text chain due to size (and the above is accurate), that would explain the low Waits/high WaitTimes for 215. Remember, as well, with WaitTimes, they are measured in 100ms increments - so a lot of fast IO's could show as high Waits/low WaitTimes......
I know you are better than this <grin> but I have to ask - given the blocking going on, did you check the KPID's??? It is possible this guy gets picked as a deadlock victim or exceeds a resource threshold (runtime) and as a result, the query gets killed - app reconnects immediately and retries - likely would get the same spid, but would explain the sudden drop in monProcessWaits.