Either a state is part of the object's identity, and it's serialized, or it's not, and it's not. This observation has nothing to do with data classes, records, Java, or Kotlin.
> The result will be equal in the `equals` sense, but the resulting object will not be substitutable for the original.
This doesn't make sense either. You are describing someone who implemented flawed serialization. It's a programmer error, not a language or semantic one.
I see very little difference of practical importance between Java's records and Kotlin's value classe, and as much as I value your technical writings, I am concerned that your employer is tainting your objectivity when trying to compare Java and Kotlin. You can do better.