You should have access without port 22 being open by opening the pfSense VM from your Hyper-V machine (assuming you are running pfSense from Hyper-V). If you cannot connect from another machine on the domain, take a look at your firewall rules to be sure port 22 is open between the two machines. If you are in a workgroup or simply behind a NAT somewhere, and the two subnets are different (192.168.0.1 and 192.168.1.1 for example), then your NAT must allow that port 22 access to flow.
The Hyper-V NIC is also sensitive here. If the Hyper-V type for the NIC is internal only, it may restrict the way the remote path can be tagged from inside the domain. (assuming it is a domain or from inside the subnet)
The three types are: External with a share for management (or with single-root I/O if the NIC supports it), then Internal and subsequently private.
If it is private, they you can only access from the machine that holds the virtual machine or in this case from your Hyper-V machine.
If it is internal, same as above but the machines that are between (I believe it means on the same subdomain) the VMs, can access the switch.