AFAIK, this discrepancy likely stems from the virtual hardware version configured for individua VMs. Even though the VMs are running on the same VMware ESXi version and physical hardware, the virtual hardware version can differ between VMs, and this affects how the VM identifies its hardware.
In particular, VMware7,1
indicates the VM is using a newer virtual hardware version (likely version 17 or higher). VMware Virtual Platform
indicates the VM is using an older virtual hardware version (e.g., version 14 or earlier). The virtual hardware version defines the capabilities of the VM, including supported features and the identifiers exposed to the guest OS.
VMs might have been created at different times and defaulted to different hardware versions based on the ESXi or vSphere version at the time of creation. If some VMs were upgraded to newer virtual hardware versions while others were not, their reported model names will differ. I gather it's also possible that the VM settings may have been manually modified during configuration or migration, leading to different virtual hardware versions.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin