Assuming the only interface defined on the CRS using ethernet was the bridge, then I don't think there is any recovery without a serial connection, or a factory reset (and losing the previous config).
The bridge interface is connected to the switch ASIC via untagged traffic over the internal trunk link. You blocked that by changing frame type to "admit only VLAN tagged".
If you had a vlan interface defined for vlan x, and a switch port with vlan x membership, and if there were no firewall rules blocking access, then you may be able to connect using that vlan interface.
But @anav brings up a valid point. If the switch was 100 miles away, how were you managing it before? Ideally you would have a VPN connection. If you had a VPN interface (like wireguard) on the CRS, then you should still be able to connect via that method. If you don't, then you are going to need to make a trip, or get someone at the remote location to be your assistant.
I can't think a way that using tagged traffic will work to the bridge interface that is expecting untagged traffic (over the switch ASCI to CPU internal "trunk link"). See
CRS326-24G-2S+IN block diagram which shows all ethernet connections are via the 98DS3236 switch ASIC. The only other access is via the RJ45 serial port.