Thanks guys. I wasn't anticipating any issues.
It'll be running on the attached host.
Unless the code is truly awful it should be able to handle the required ~2.2 Gb/s throughput that's the maximum it might have to deal with.
As this is a technically minded forum I'll just outline what I have in mind - bearing in mind this is for the new home that I never plan on moving from unless horizontal!
In the Harry Potter room (cupboard under the stairs) will be a
https://mikrotik.com/product/crs309_1g_8s_in taking in 2 WAN feeds on GbE ports and sending them to the host via a 10 GbE port. This 10 GbE port will have VLANs for each of the WAN links and a native VLAN for LAN-side traffic.
In my home office will be another CRS309_1G_8S. This will use 2 * 10 GbE ports for connecting back to the Harry Potter CRS309 and forwarding the 3 VLANs to the VM. The rest of the ports will be populated as needed with SFP+ on the native VLAN, initially another 10 GbE for wireless AP which also has 6 GbE ports for use on the home network.
EDIT: I could use the 5 port versions of both however the cost difference between them made me inclined to spend a little more rather than having to buy more 10 G-capable switches later and cascade.
The 10 GbE NIC on the host will be segmented into the 2 * WAN VLANs feeding vNICs on the pfsense host and the native LAN VLAN. The native LAN VLAN will be rate limited to 7.5 Gb/s outbound on the switch to avoid it impinging on the WAN.
The pfsense host will also have a 'lab' interface - this will be to a virtual switch connecting to the VMs terminating my lab network internally on the host only. Those will have WAN vNICs on the vswitch the pfsense lab interface is on, segmenting the lab network from the rest of the home network.
A simple TP-Link smart switch and the existing GbE ports on the host - 2 built in will be fine as I'll be replacing the 2 * GbE NIC on PCI-E with a 10 Gbase-T - will serve as lab port density.
This lab is where the SD-WAN will also happen. The only traffic heading to the Internet from here will be control plane traffic for the SD-WAN and its own proprietary tunnels. There will be some static load balancing rules to pin traffic from the respective SD-WAN appliances to each WAN link.
Nothing too complex: just takes a little time, care and attention to make sure I don't mess up the virtual network configuration.