Currently, application connections use connectTimeoutMS for the initial connection establishment and then use socketTimeoutMS as the timeout for all subsequent reads/writes. It may be more robust to use connectTimeoutMS for the initial isMaster handshake and authentication commands (instead of socketTimeoutMS) to detect failures quicker.

Note that this is lower priority because:

1. The connection was just established so it should be rare for the initial isMaster to timeout.
2. DRIVERS-555 Client Side Operation Timeout should eliminate this concern by unifying all timeouts.