I honestly don't know what the issue is wrt your WOL failure (although I have a suspicion), but let me make a suggestion.
Several years ago I decided to get off this dependence on WOL and instead use wifi-enabled AC adapters. What I do in the case of a desktop PC is enable "Restore from AC power" in the BIOS (it may be named differently w/ different BIOSes) so that when the AC adapter is turned ON, the device is automatically booted. When I'm done, I shutdown the device and power OFF the AC adapter (or just leave it ON and power cycle it later to boot the PC again).
This effectively provides WOL to just about any kind of device imaginable. I happen to manage my OpenVPN server on a separate router that's connected to such a wifi-enabled AC adapter. I keep port forwarding enabled to its LAN IP address, but it remains unreachable unless I power ON the AC adapter, which I can do remotely and on-demand w/ my iPhone, making it much more secure (since the WOL function assumes you've enabled remote access to the GUI of the primary router, which is NOT recommended).
As a bonus feature, let's say the PC (or whatever device it may be) hangs. I can now just simply power cycle the device w/ the AC adapter! That alone has made it worth the investment.
Again, this obviously is NOT directly addressing your WOL issue, but imo, WOL is an outdated, arcane, and insecure way to deal w/ this type of problem. And given how cheap and common these wifi-enabled AC adapters have become (I picked up about a dozen a few years ago for $5 a piece on sale), it's just the better solution in most cases. All this nonsense w/ BIOS settings, making sure it's enabled in NIC's driver in the OS, dealing w/ expiration of the NIC's MAC in ARP, WOL not working w/ wireless, etc., is such a PITA. I just don't deal with it anymore. Once you have remote control of AC power, all that nonsense w/ WOL becomes a thing of the past.
JMTC