Making ARP Table Immutable?

Since Dnsmasq has been added to OPNsense I've been using it without zero issues then sometime last week (I need to keep an issue log) either the day of the 26.1.3 update or the day before my wake on lan for my computer suddenly stops working. When I started troubleshooting I discovered that the machines ip and mac were not staying in the ARP table meaning it couldn't find the pc to wake up. I would love an explanation about how something can work for months then just stop. I'd assumed that setting a static ip in dnsmasq also created a static ARP as well, but I guess not. I mean all my useless IoT crap (TV's, robovacs, etc) stays in the ARP no matter what but not regular computers.

As it stands dnsmasq is working like KEA meaning for my ARP needs not at all. I tried to use Neighbors as the documentation says "IPv4 entries will be saved into the ARP table". Which I can tell you right now isn't true. I have a static assignment of ff:ff:ff:ff:ff:ff 192.168.20.254 which doesn't appear in the ARP table at all.

I notice that there is this issue on the tracker but I don't have the time to wait for 26.7 to come out in the hopes that it gets fixed. Is there some way to mark the ARP as immutable (chattr -i)? Or maybe a cron job that adds the mac and ip to the table every hour (or less)?