Bro, pack that up in a ticket and send it in. the GMs don't give a **** about what is written in the forums. This is the only way they will even consider suggestions.
Sadly the game client is not moduilar and can't to do 3-part operation
(part 1) Login - HTTPS request to a web app which drives...
(part 2) Server selection - 50/50 Web call and stored procedure call to MSSQL which hands off to ...
(part 3) Game server connection from address obtained in part 2. This is what ultimately connects to the game client using a custom session.
The problem is that parts 1 & 2 happen in a web server. The transaction is ephemeral. Once the server hand-off happens, the http session ends and the socket is released for someone else to log in. The web session can not be passed on the actual game server component, and the http session must be released to accommodate as many players as possible. Hanging on to http sessions for several hours (or for some players days) is never a smart thing to do in client/server communications.
part 3 (the game server using a custom protocol) has no idea how to re-establish a destroyed web session and call the server selection web app without forcing another login.