When adding a new shard, the config server sends several requests to the shard using a separate task executor, like isMaster, listDatabases, and a drop of the sessions collection. These requests are not retried on network errors, or any retryable errors, unlike commands run through the Shard interface.

It looks like prior to 3.4, a different code path was used for these requests, that did retry on retryable errors.