IMHO, if you use 23, 25, 50 or 100ms timing , it makes no difference to DMX, what makes a difference is you must keep all the events synced to that timing. The variable timing option should not be allowed for DMX.
If converting a sequence from one program to another and using DMX, variable timing events have to be converted to synced timing. That means the conversion software might have to make a decision on some events to turn them ON or OFF a few millisecond from the variable time.
Not everyone uses thousands of RGB channels, and file size is not the problem for some, but using non synced events is a problem.
It took me 3 seasons to figure this out in my display.
LOR's protocol is fine for LOR equipment, it only sends commands when needed, that is a non-synced protocol for their devices. I know LOR is trying to convert the output to synced DMX, but something is still not right.
All the equipment in my display appears to accept the faster data, almost all is Lynx equipment, The 4 CCR Circles seem to like the 25ms timing also, my wife even says they look so much smoother doing the SuperStar programming.
Knowing the equipment limitations of each piece of your display will help you decide what maximum timing should be used. If using wireless and the wireless only can handle maximum 50ms then do not try to send data faster than that to that portion of the display.
Remember a chain is only as strong as its weakest link.