SERVER-81863 forgot to also consider cases where alwaysFalse is nested within elemMatch. As a result of that, and in combination with SERVER-70477, we caused a regression identified in HELP-75546 where a query like {$elemeMatch: {$in: []}} is now translated to {$elemMatch: {$alwaysFalse: 1}} and thus requires COLLSCAN since neither index bounds can be applied nor an EOF plan is considered.

Unfortunately hinting the right index doesn't work either since a full IXSCAN would be required