Windows 11 OpenVPN TAP Configuration Creates Wrong Routing Table Entry

[opnsense noob]

I have configured a VPN using OpenVPN with Tap interface.  I am using a bridge for this configuration.  I have IPv6 turned off.  Likely irrelevant to this topic but it reduces potential red herrings.  Everything appears to be working correctly HOWEVER, when I use the OPNSense DHCP service I get handed an IP within the range I am expecting HOWEVER cannot connect to my private network.  When I use the OpenVPN DHCP service, then everything works fine.  This is configured in Server Bridge DHCP Start / End. 

Now, I compared the route table on the client between these two configuration and find that I have an additional (and incorrect, I believe) route entry when I try to use the OPNSense DHCP service.  I cannot find where this route entry is coming from however I think this is the cause of the connectivity issue (please help me identify the solution!).  I attached the table in a file.  For this example, I connected from a hotspot as a source of remote connectivity.   

I can provide more details (config files, etc. as necessary but didn't want to clutter this topic up unless necessary. 

I am running the following:

Server:
OPNsense 23.7.1_3-amd64
FreeBSD 13.2-RELEASE-p2
OpenSSL 1.1.1v 1 Aug 2023

Client:
OpenVPN GUI v11.31.0.0 Windows Gui
OpenVPN v2.5.8 - I installed this version because 2.6.x appears to have compatibility issues with the above version of OPNsense