While working under the task https://jira.mongodb.org/browse/SERVER-95448 the question arose:
if the optimization to break the loop of shard key ranges can continue to work for chunk ranges. This optimization was added before the chunk ranges handling via

QueryTargetingInfo* info 

was added and it would be good to check if after this break not only shardIds, but also chunk ranges will correspond to the given min/max values. For example the next BSON range value from the BoundList will correspond to the same set of shardIds, but can have wider range, like

min2 < min1 < max1 < max2
Please check If the question makes sense.