While working on SERVER-88099 we found out that the FSM worker thread will only synchronize mongos cluster times if it happens to use transactions.

However, ideally we should always do so on sharded clusters generally. Reading at a snapshot readConcern could make a stale mongos choose a cluster time from before the setup completed, thus leading to an incomplete view of the data that tests assume is present.