What's the reason to disable the functionality to ask to be inside within a fraction of uncertainty outside of the proper bounds?
I don't see any downstream changes in use cases: did we have no use case at all?

This is a general geometry class. If the matching within nSigma tolerance is an issue in use cases in the tracking, I'd expect that the tracking code is changed.

This now looks broken to me.