The analysis of SERVER-108140 shows that currently CBR does not consider plans using potential sort index for the entire query. The sort index is considered only for each individual subquery and then discarded during plan tagging, since we don't allow whole index scans for $or branches..

See for example query q0063 from the synthetic benchmark.

Adding these plans to the enumerated space and choosing between them and the best subquery plan can solve this problem.