Seems like the best hotfix would be...

To fix the strange 2002 disconnect while folks are in the queue. I think people would be okay with the idea of a long queue, but not when you get to less than 1000 and you just get a random 2002 error that puts you back at 6500 once you get back in. The official communication says that this is on the client end (like my network connection drops); but I don't think that's the case since I've seen hundreds of posts with the same problem. Everyone's network connections can't all be bad, right?

(Also, completely quitting the executable every-time a 2002 is encountered is grating, especially if you have a One Time Password)

I completely agree with this. I have switched from a wireless to a wired network connection, and run not one, but TWO different network activity sniffers, and can safely say I am not getting the 2002 error due to packet loss, or network stability issues.