Yes, what you defined was already very obvious.
With the usage plan you have and the equipment you plan on using then that's the only real seamless way to get what you want.
If you used the LAN port on each device, all of your hosts would be on the same subnet, so it wouldn't matter which SSID they connected to. You'd have to manually juggle host routes on each PC to flop between the VPN gateway and the non-VPN gateway.
Bridging your current router is also a fail since you will lose connectivity for other hosts out of your non-VPN router as the VPN router will be the only device obtaining a WAN IP.
I don't understand what an unmanaged switch would give you in the context of wireless and SSID segregation.
If you had equipment for VLANs and access points that could broadcast multiple SSIDs (which would actually be preferred), you'd also have to add some PBR policies on the gateway to indicate 'the next hop for traffic from this VPN-secure SSID subnet goes over the tunnel instead of the internet'.
Using the LAN->WAN approach provides your VPN subnet with its own unique subnet behind a NAT of your original network. The router can form the VPN tunnel through the NAT (usually known as NAT-T) and any clients connecting to that SSID can utilize the tunnel as their default gateway is the device with the VPN tunnel that terminates on it, without having to change anything on the client device.
I think it would cut my speed in half?
Please provide a technical reason why you believe this.