Why can an Android Jellyfin client reliably wake a Windows 10 PC but not Linux?

[The Cake]

I think I discovered the issue but am unsure how to fix it.

The built-in network adapter on the PC in question supports a feature called "Wake on Pattern Match" which will wake the system on any TCP connection attempt.  It appears to be efficient at filtering out "noise," as such I never noticed it until troubleshooting this.

“Wake On LAN” makes the system wake on the “magic packet.”
The “Wake on pattern match” option instead checks for packets that matches the operating-system-specified patterns; for example, an ARP request for the computer’s address, or a TCP connection attempt.
The default patterns on a Windows 7 system are:

• Magic Packet.
  
• NetBIOS Name Query.
  
• TCPv4 SYN.
  
• TCPv6 SYN
  
• IPv6 Neighbor Solicitation.
  

It seems Linux (the driver probably?) does not support this, at least this distro (Mint 22.1) for the adapter I'm using (Intel l219-lm).

Code:

sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes:  10baseT/Half 10baseT/Full
                        100baseT/Half 100baseT/Full
                        1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  10baseT/Half 10baseT/Full
                        100baseT/Half 100baseT/Full
                        1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
[b]Supports Wake-on: pumbg[/b]
Wake-on: ug
    Current message level: 0x00000007 (7)
                          drv probe link
Link detected: yes

The ethtool documentation mentions "Wake-on-filter(s)" which I'm guessing is the same thing or similar?  Attempting to enable it with ethtool returns that it's unsupported.

Code:

p Wake on PHY activity
u Wake on unicast messages
m Wake on multicast messages
b Wake on broadcast messages
a Wake on ARP
g Wake on MagicPacket™
s Enable SecureOn™ password for MagicPacket™
f Wake on filter(s)
d Disable (wake on nothing). This option clears all previous options. 

Going to mess around with finding appropriate drivers as a last ditch effort, but it seems like intel stopped updating the driver years ago.

I know this is probably outside the scope of this forum at this point, but does anyone have any experience setting this up on Linux or know of any hardware that supports the wake on pattern match feature on Linux?

This is incredibly useful for Jellyfin or any kind of NAS application, I'm surprised I can only find mention of it from people troubleshooting their device randomly waking up.