Currently, the SdamServerSelector has the logic to ignore the minClusterTime in the readPreference given to it if the timestamp is not satisfiable. When constructing the effective readPreference, it only gives 'pref' to the constructor. Consequently, the other configurations such as 'tags', 'maxStalenessSeconds', and 'hedgingMode' all get lost.  For shard remote targeting at least, minClusterTime is only specified when the shard is the config shard. Prior to PM-2290, there probably isn't a case where the config server is targeted with readPreference that contains tags and so on. That might be why this issue never surfaced. Starting from PM-2290, this is a bug that needs to be addressed since it can result in the external client readPreference not being fully respected (as shown in BF-27925),