Here is the KB related to this :VMware Knowledge Base
With latest vSphere releases, there is little change in vMotion and EVC behavior if your cluster has some hosts does not have these patches applied.
Quoting from KB:
vMotion and EVC Information
An ESXi host that is running a patched vSphere hypervisor with updated microcode will see new CPU features that were not previously available.
These new features will be exposed to all Virtual Hardware Version 9+ VMs that are powered-on by that host. Because these virtual machines now see additional CPU features, vMotion to an ESXi host lacking the microcode or hypervisor patches applied will be prevented.
The vCenter patches enable vMotion compatibility to be retained within an EVC cluster.
In order to maintain this compatibility the new features are hidden from guests within the cluster until all hosts in the cluster are properly updated. At that time, the cluster will automatically upgrade its capabilities to expose the new features. Unpatched ESXi hosts will no longer be admitted into the EVC cluster.
Can you confirm whether your source cluster has all hosts patched with build you specified i.e. 7967664 ? Post applying these patches, whether power cycle was done? Whether your destination cluster has all hosts with "8169922" build?
Are these fully updated? There are non critical patched for cpu microcode which can cause this, it was for the spectre/meltdown patches. Looking at your information
Source is ESXi 6.0 Build 7967664 (Latest)
Number of microcode updates:1
Destination is ESXi 6.7 Build 8169922 (Latest)
Number of microcode updates:0
The destination doesn't have microcode updates listed. If you have update manager, check the non critical update baseline. See if there is a cpu microcode patch that should be applied.
6.7 may or may not need them, I just don't have one to check.
Below articles will help you to understand vMotion and EVC behavior post the patches you applied.
1. Confirming whether entire EVC cluster is patched or not and see new cpubits are available on all hosts (new cpu bits got introduced into these patches)
2. This is again related post: http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/