I can comment on that as I've had hibernate and fast boot disabled for ~15 years now that I've been using WoL on Asus/Intel boards. This problem started for me even with those already being off. I don't know what board you have but if you don't have the i225-v, those changes could indeed resolve problems.
My i225-v (v3) worked for months until a certain BIOS update came through for my Asus Z590-i. The issue started within days, that's when I knew (Intel) changed something. I did roll back the BIOS but this will only rollback the core, as Asus doesn't package and intend to flash the network device's firmware when you rollback (or typically, ever). Without someone putting together an update to resolve the i225's issues, it's a one-way trip when you upgrade your BIOS for sub-systems like networking. They only modify what has changed. Without Intel pushing out an updated BIOS package, going back today would require a full on-chip firmware wipe and reflash (rather than the partial updates that BIOS releases consist of). Only Asus or potentially Intel can do that as you need to flash the chip physically on the solder points / pins on the motherboard or NIC, with a hardware flash device.
The fact that clearing the NVRAM mysteriously fixes it for all of us by pulling the power plug proves it's Intel's problem. There's too many of us. They've got something becoming corrupted or losing state over long periods of time. My WoL will work for 5 to 7 days straight, and then it won't work any longer until I pull the power plug. Restarting the machine, powering it down/up, does nothing. They'd love to blame it on the board and waste my time and energy on an RMA, but again, there's too many of us.
It's all about whatever they're doing in the non-volatile RAM on the i225-v. We have them dead to rights, so to speak.
