This is caused due to vCLS VMs getting re-deployed after patching the vCenter Server.
This is an expected behaviour after vCenter Server patching. These VMs are System Managed and will get redeployed to take new build configuration. The VM reconfiguration tasks for vCLS VMs will stop after some time once all the Clusters in the vCenter Server are configured with the new vCLS VMs and no manual intervention needed.
Refer vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 and newer versions for more information on vCLS Virtual Machines.