Sure!
Honestly, I had to take a look into the code to remember the purpose 
The TimeOutMs on the left side belongs to the COM-Port. This is a property from the SerialPort class in .Net. It will set ReadTimeout and WriteTimeout, if unequal to 0.
Offset values are not in use... I guess there was some missunderstanding with the throttle position values. Just ignore them 
The ECU timing is specified in KWP2000, in detail by ISO14230 and/or SEA J2190. It might be changable on the ECU, but I think it´s not supported on most bikes.
Many implementations somehow rely on those specifications above, but none of them really implements it completely. Take it as an approximation, not a documentation 
But in short: There must be a delay between sending the bytes (5ms), the messages (~120ms) and even receiving.
Mostly ignoring those timings, the ECU will not respond for about 100ms. Plus request, echo and response, you won´t get far below ~200ms.
The best I did were around 7 messages per second (Kawasaki). But not very reliable. I ended up with 55ms between the requests and 5ms between sending the bytes.
Due to hardware serial, I just read whats there, ignoring any timing.
The Suzuki is slower due to bigger messages. But they include several values at once, so you can speedup the process by storing them temporary.