Ah ok, thank you very much..
I already googled a solution like that but wasn't sure if this additional route will effect the "main" route (to 0.0.0.0/0)
/ip route add distance=1 gateway=8.8.8.8 check-gateway=ping
is the same as:
/ip route add dst-address=0.0.0.0/0 distance=1 gateway=8.8.8.8 check-gateway=ping
So you would get rid of your existing default route (to 0.0.0.0/0 through ether1) and replace it with that. If the existing default route through ether1 is received through DHCP then you will need to disable adding the default route in the DHCP client settings.
Then, the other route needs to be added to explain how to get to the fake "gateway" 8.8.8.8 (otherwise you won't actually have connectivity):
/ip route add dst-address=8.8.8.8 gateway=you.rga.tew.ay scope=10
If your ether1 IP is received through DHCP and it is possible that your default gateway might change though ether1, you might need to script the update of that route in the DHCP client. If your ether1 IP is static, or the gateway is always the same, that is not necessary.
Leave your LTE default route in place, just set it for a distance greater than 1 (ex. 2, or 3, or whatever you wish)
If you want or need to do a similar ping test for the LTE gateway it is possible, but I'm guessing it isn't necessarily since the LTE is really a fall-back anyway.