I've had a ticket this week (02100004) which was about Veeam failing with WMI errors on our 2016 Datacenter Hyper-V cluster after installing KB4013429. Uninstalling that patch resulted in a BSOD bootloop, so the host had to be reinstalled. I've been able to reproduce that issue several times. On some hosts uninstalling works fine, and after uninstalling WMI / Veeam works fine again. This ticket was closed as it's clearly caused by KB4013429, so it's a MS thing initially. However, today I stumbled on this post
where someone has the exact same issues after KB4013429. This also happens to be on Datacenter, not sure if that would be the common denominator here. Also, on my site it only happened on clustered nodes, we also have standalone hosts, and they are still fine after installing KB4013429.
So I just want to warn you, do proper testing before rolling out KB4013429.