I see what you're trying to point out, but keep in mind that the basis for checking individual records is 1:1 because the lookup is joined on the primary key, therefore, you're not checking against the entire dataset, which could create the behavior you describe.

I am interested in seeing which specific changes to a record could result in generating the identical MD5 checksum.