Looking into this some more, I know one person who also has DisplayFusion in their list, and found this thread with some more examples including TortoiseGit and TortoiseSVN:
It seems like Chrome is simply listing just about anything that might cause a DLL to be loaded into the Chrome process, which is going to result in a lot of false positives. Lots of things do that as it's a normal part of the Windows API for it to happen for certain types of functionality.
Sure enough, if I make Chrome open a File > Open dialog (e.g. menu icon > More Tools > Save Page As...) and then do something which causes the TortoiseSVN overlays to be loaded for a folder (which loads a Tortoise DLL into the process to supply the icons), Chrome starts listing TortoiseSVN in the list of incompatible applications, despite no problems being caused and it not being detected as a problem a moment earlier.
I think Chrome has just lots its mind temporarily with this update / detection method. Hopefully Google have enough reports in their forum and are looking at why it's listing so many different things without reason and will fix it soon.