Found the issue, rookie mistake,
Hardware Checksum Offloading,
Hardware TCP Segmentation Offloading,
Hardware Large Receive Offloading
Where not checked so they were enabled, forgot to check these to disable them.

Glad you found the issue. I could not remember off the top of my head whether "unchecked" was enabled or disabled for those parameters, so sorry I missed that in my previous reply.

When Suricata starts up in IDS mode, the first thing it does is call the PCAP library to initiate a capture of traffic on the physical interface Suricata is configured to monitor. My educated guess is that sequence of events is disrupting the NIC driver in some manner. This would impact unbound and dhcpd because those daemons are tied to the underlying physical interface. If the network interface driver gets "stuck", then it stands to reason any other daemons bound to that interface will also experience problems.

If you have a different NIC port to test (one that uses a different controller and driver), then try running Suricata there to see if it works. Also, unless you are running on a Hyper-V hypervisor, then you don't need the hn ALTQ support enabled.