I have the wifi2 (2 GHZ) adapter running as AP in a bridge, internet by WAN/ether1. mode "HOME"
This works well.
I would like to make a 2nd wifi2 interface (not active /enabled at the same time , mode "TRAVEL").
to provide internet connection instead of WAN/ether1 .
In principle it can be done.
But using the same radio, say with the real wifi interface as Station (or Station-pseudobridge) and an added slave virtual interface as AP, will roughly halve the throughput.
So on an already slowish 2.4 GHz radio you won't have much speed.
Then it is just the case of having a script of some kind to alternate between two configurations.
If you have a device with a "mode" button - you could "link" the button to the script, while having (as well if your device has it) the "user led" as visual indicator of which configuration you are running[1].
I would start making a "HOME" configuration (and test it thoroughfully).
Then making a "TRAVEL" confioguration (and as well test it thoroughfully).
Then it will be just a matter of finding the differences between the two with something like (shameless plug ):
If you use properly the default rules, they are based on interface categorization, you change the categorization of interfaces leaving firewall rules untouched.