Hi @Delta_Ark,
first of all, welcome to the community! You can go ahead and Introduce yourself 🙆 if you feel like it!
As for your question, I see you’ve already semi-answered yourself:
There is a certain amount of time that is spent converting the Rhino objects to Speckle and sending them through the internet. I’m not sure you’ll ever get real-time communication via commits unless the amount of conversion/data sent is tiny, as they were not designed in that way (this would apply to almost anything really).
A commit is a Snapshot of all the data at a particular moment in time, the more data you send, more time would be required to process it. If you were to do this at 60fps, that would result in 3600 new commits per minute of “permanent” data.
Right now there is not, but I am aware @Kateryna has done some magic with the viewer in the past to get it to run animations based on the data of one single commit; meaning instead of sending one commit per “frame” you send 1 commit per animation, with all the information for each frame included. I’ll let her point you in the right direction for that 
Final thoughts
After sending you my reply i realised you could get every frame sent if instead of using the Send node you used the Send Sync node.
This node will “block” the execution of the GH solution until it has finished, therefore it should prevent any other thing from happening until it has finished sending its data.
That may solve your “missing frames as commits” problem, but it still won’t really fix the “real-time” communication issue. 
Maybe @dim has some thoughts on this