WIth all due respect, I am not too convinced.
Possibly it will become the fourth best thing in the world, after bread, ice cream and grub4dos, but right now there are too many unclear, confusing or downright wrong claims.
Hopefully it will evolve/mature.
It is not clear at all what the thingly does (or should do) it seems like it is a replacement for the bootmgr.efi, but the SeaBIOS is involved, so maybe it is a sort of software CSM (that would be a great thing) if not then it is not clear the mechanism about using (or replacing) winload.efi (on EFI systems) or winload.exe (on BIOS ones) nor how (the heck) it would load XP that use neither, there is a reference to freeldr.ini so maybe some files form ReactOS are used for this.
Facts (only for the record):
Windows XP is fine on FAT32
Windows Vista on FAT32 can be done with a couple tricks
Windows 7 on FAT32 can be done with a couple tricks AND greatrly reducing the WinSXS directory contents (reduction that may leave the 7 only partiallly functional) <- this is a FAT32 filesystem limit that does not allow too may files in a directory
8 onwards is likely not possible at all because of the above FAT32 filesystem limit
Interesting an IMHO we should keep an eye on this, but at the moment possibly only useful if you want to boot a Windows 10 on BTRFS (a rather niche activity, I would say).