Lemme try this again… yes, sorta? An example would be a lock such as os_unfair_lock or pthread_mutex_t where the bits of the value might be the same, but the address of the value provides its true identity. So the bits of two values may compare equal, but you cannot interchange them.
I don't know if that satisfies the constraints you're thinking of though, since the address of a value is not an innate property of the value itself (doubly not so in Swift.)