Hey,
Regarding your original question. The router will determine whether the wan link is active using Track IPs, which you can configure in Failover configuration.
The router will ping those IPs; if they are not reachable, it will switch to the backup wan interface.
By default, those IPs are 8.8.8.8 and 1.1.1.1, so if you can not ping 8.8.8.8 from your router and you're using default track IPs, there is no wonder that the main wan interface will not be active, as the router will be switching to backup wan.
It would be best if you changed the Track IP to ISP DNS server for proper configuration.
Now, as far as I know, only one wan interface could be fully active on the router, and what I mean by saying that, you can enable load-balancing on multiple wan interfaces, allowing traffic to flow through different wan interfaces based on the radio you configured, but the router will only be reachable via main wan IP address.
Here, I might be incorrect, but if you have another router available to you, you should be able to test it with ease, by enabling load balancing on wired and mobile wan, (wired wan working as the main wan) and try accessing the router via mobile wan IP (here you might need public IP).
If you need dual access for main wan debugging issues, maybe changing Track IP will resolve it, another way would be to use failover. Once your main wan will go down, you will be able to access the router via mobile wan. If you do not have public IP on mobile wan, you can use a free VPN service as a Zerotier, which you can install via the package manager and find needed instructions on the wiki.
If you are worried about high mobile data rates, try using QoS to reduce traffic speed on the mobile interfaces by only allowing traffic via SSH interface for debugging using firewall rules. In order not to exceed mobile data limits, use the data limit feature on the router.
It is not a Mikrotik packet marking level solution, but it is the best thing I can think of.