This is a horrible idea that could very easily be abused to get an edge in-game.
Also, I have my doubts on its possibility, simply because if you understand what a disconnection is, it's the program crashing, and how could we possibly make our game execute code after it's crashed?
The only work-around is if only the bout executable itself crashed, enabling ZylonShield to detect a crash, and auto-reset client. However this wouldn't be an efficient method because zylonshield is injected into the bout executable, thus meaning if bout crashes, it crashes.