Users may use the shell to check on nodes that are in states besides PRIMARY or SECONDARY, e.g. STARTUP2 or RECOVERING. Right now it seems due to https://github.com/mongodb/specifications/blob/c378d48de4da1a4f1438dc30c1bf464ae9f9cd7c/source/driver-read-preferences.rst#read-preferences and https://jira.mongodb.org/browse/DRIVERSOLD-1 the driver refuses to connect to servers that are in such a state. We will need a way to circumvent that limitation so users may connect using the shell.
If the driver does not support this use case, it means the MongoDB Shell can't be used for a number of cluster administration purposes and can't be used as a tool to bring customers back online when something bad happens in a cluster or on a node.