Did some digging...
Misfire trips - confirmed - 2216dc however the equation is probably (A*256)+B. It is returning two bytes of data so while just a "B" equation will work it will max out at 255 trips. If you want to see a higher number than that you will need to use the full equation.
Number of Misfires during recent misfire "event"
PID 220345 (as indicated previously) however the equation is returning 4 bytes of data which means it can use the variables A, B, C, and D. I was only able to experience a single misfire event in a 45 minute drive and the D variable showed a 1...as did Forscan. So...and it's a guess at this point...You could probably use (C*256)+D to get you a guage that would read up to 65535 events...which would certainly be sufficient to let you know that you've got a big issue...(in theory you could represent over 4 billion misfire events with all four variables...Pretty sure your car wouldn't be running then.)
All of this was just from Forscan...I haven't verified any of it in Torque yet and probably won't until after work. If anyone wants to try it out let me know how it goes!
I did find another PID which was "Misfire currently detected" that looked interesting but Forscan interpresets a value of 00080000 as a "No". Not sure what a yes would look like yet but maybe I can catch one. The PID is 220700.