Good luck trying to report your possible bug on a community forum where the staff are not active. These are so minimal and the priority is so low. Considering their track record, these will most likely be in a deep backlog somewhere for the next 20 years or something if they considered your suggestion.
Did you consider that the asymmetric comparison was intentional and not a bug? Adding a break in a simple loop like these can save some iterations, but modern CPUs can do millions of floating-point comparisons per second. Even the overhead call for ApproxCompare is minimal. The savings is probably small in microseconds to seconds and the performance gain is probably not meaningful.