It seems that Process Reimaging is related to some vulnerable Windows APIs which can retrieve file name and file path of already running executable. So any AV which uses those APIs is vulnerable to this attack, too. In June 2019 M$ has released a partial patch, closing file name attack vector in Windows 10. That is why the video was published a year after disclosing the vulnerability.
"McAfee Advanced Threat Research submitted Process Reimaging technique to Microsoft on June 5th, 2018. Microsoft released a partial mitigation to Defender in the June 2019 Cumulative update for the Process Reimaging FILE_OBJECT filename changes attack vector only. This update was only for Windows 10 and does not address the vulnerable APIs in Table 1 at the OS level; therefore, ESSs are still vulnerable to Process Reimaging. Defender also remains vulnerable to the FILE_OBJECT filepath changes attack vector executed in the bypass demo video, and this attack vector affects all Windows OS versions."
Windows ver. 1903 is also vulnerable to this attack, but it is harder to perform because of Tamper Protection. The attacker has to use the 0-day exploit for Process Reimaging and 0-day payload (in place of Mimikatz). The attack with Mimikatz will fail if WD is not temporarily disabled.