Iām all torn up in production mode, so I donāt have any stats handy either. I remember there being a discussion about this in the past on the forum, but I have been unable to search and find the relevant posts.
My experience is that communication is quite swift. I only was able to perceive a flam when I had 8 TXo connected and was sending a number of commands to each one at the same moment. I was torturing it on purpose. 
Something like:
M
L 1 32: TO.TR.P I
L 1 32: TO.OSC.WAVE I RAND 45
L 1 32: TO.OSC.N I P RAND 32
L 1 32: TO.ENV.ATT I RAND 30
L 1 32: TO.ENV.DEC I RAND 250
L 1 32: TO.ENV.ACT I
In the example, there are a lot of commands between the PULSE and the ENV.ACT commands, which could put a delay between them. It all comes down to how many sensitive commands you are trying to send at any given moment.
Iāve been able to solidify the timing by using the DEL operator to better fix the timing of the things that produce the sounds and then do the setup in the intervening window. For example:
8
L 1 32: TO.TR.P I
L 1 32: TO.ENV.ACT I
M
DEL 15: SCRIPT 8
L 1 32: TO.OSC.WAVE I RAND 45
L 1 32: TO.ENV.ATT I RAND 30
L 1 32: TO.ENV.DEC I RAND 250
L 1 32: TO.OSC.N I P RAND 32
This gives the setup the time to take the time it takes and the āsound activatingā commands are sent as closely in succession as possible. (The length of the delay depends on what you have going on. I just picked 15ms for this example.) Think of it as the breath that wind players take before the note sounds.