Personally I have a Linux and MikroTik background, so I would go about setting my home LAN untagged/PVID on the port, and then tag the isolated lab VLAN, thereby making it a hybrid port.
Then I'd configure the VLAN on my NIC in my computer's OS - granted that's a lot easier to do in Linux (and perhaps macOS) than Windows.
That'd be my preferred method, but I have no idea if that can be performed across different switch vendors, and if desktop versions of Windows natively support VLAN tagging at all (without any third party utilities or special NIC drivers).
Another option that'd be silly but works: grab a second NIC. If you're on a tower desktop, i225 PCIe NICs are readily available on Amazon (IOcrest makes some nice x1 cards). If you're on a laptop - dongle time!
Soooo it depends on a few things...
Personally I have a Linux and MikroTik background, so I would go about setting my home LAN untagged/PVID on the port, and then tag the isolated lab VLAN, thereby making it a hybrid port.
Then I'd configure the VLAN on my NIC in my computer's OS - granted that's a lot easier to do in Linux (and perhaps macOS) than Windows.
That'd be my preferred method, but I have no idea if that can be performed across different switch vendors, and if desktop versions of Windows natively support VLAN tagging at all (without any third party utilities or special NIC drivers).
Another option that'd be silly but works: grab a second NIC. If you're on a tower desktop, i225 PCIe NICs are readily available on Amazon (IOcrest makes some nice x1 cards). If you're on a laptop - dongle time!