At the moment this is not "officially" supported, but I believe you might succeed with a bit of hacking.
You first need to establish a successful connection and then reset the reconnection timer by calling sfs.SetReconnectionSeconds(0)
is whatever your SmartFox API instance is called.
It's not doing either of these. As you say, something has gone wrong with the TCP mechanism and it's not in a proper reconnection phase but HRC is causing it to do something differently as I get different experiences with it on and off.
Yes, I thought I was clear enough in my previous posts.
It is the same as saying that if the sensors of your house alarm (TCP) don't detect an intrusion the siren (HRC) won't go off and someone might be able to get inside undetected.
In other words HRC relies on accurate event dispatching from the TCP stack. Should this fail, it's expected that HRC might fail too.