isQuerySbeCompatible showed up as the cause of +0.61% CPU time growth in a comparison between v6.3 and v6.0. There are a few easy fixes, first there is a tassert followed by an equivalent invariant, then there is potential for an early return. If isQuerySbeCompatible has a noticeable perf impact, these changes are worth making.