It’s not me, it’s the script’s author who thinks so.
Whether this can be corrected for, I don’t know. The simplest place to collect lost races data would be uplink, because this is the code that actually implements the race. But right now there’s no communication on these results implemented. AFAIU in some circumstances the notification on dropped connection might be delayed by many seconds, maybe even minutes, so trying to work it around might be difficult.
EDIT: after thinking about it a bit, it might be even more difficult. Both uplink and node may close connections not knowing about the other side also closing connection. Then, even if uplink closed connection earlier, the node’s OS may simply ignore uplink’s closing connection because the node already closed it as well. You’d probably need to ask someone experienced with socket libraries across different OSes to have an answer.