I think this is muddying the waters. As explained in the documentation for Equatable, identity is not equivalence. Those are two distinct concepts. We should not use conformance to Equatable (i.e., a notion of equivalence) to be a proxy for judging whether instances of that type have a notion of identity.
As far as I'm aware, Swift always provides the most correct implementation as the default or currency option. Those who wish to opt into more performance can explicitly invoke alternatives (e.g., unsafeAdding vs. +).