@normis has a point: most of the cost on Chateau LTE18 is for the LTE modem. So if LTE is not needed, it's not a great choice.
e.g. while starlink is within its routing abilities, it's not a powerful router. A hAPax3 is more powerful router, and has more internal storage, if no LTE is needed.
Although Mikrotik does offer QuickSet profiles to convert the config, so it's not hard to use Chateau with Starlink or WAN.
So assuming it the defaults, you should be able to use QuickSet to switch it's mode.
1. Go to QuickSet in webfig or winbox.
2. In the upper-left of QuickSet, there should be an option for "Home AP Dual", select that, and it with migrate the default to have ether1 be a WAN.
3. Make sure the "Firewall Router" box is checked under "internet" and should show the starlink address above that assuming ether1 goes to starlink
4. Under "Local Network", check at "DHCP Server" and "NAT" checkboxes
5. Verify the IP Address is 192.168.88.1 (or whatever subnet you'd like) and the DHCP range matches that subnet (so 192.168.88.100-192.168.88.199 or something).
6. Optionally, check uPnP if you have gamers or VoIP.
7. Hit OK in QuickSet
Now it's possible the Chateau LTE18 does not have the "QuickSet" profile for "Home AP Dual". If not, you need to:
1. remove ether1 from /interface/bridge/port
2. add ether1 as WAN under /interface/list
3. in /ip/dhcp-client, add a new one with interface of ether1, defaults should be fine
4. at this point the ether1/starlink will have priority for WAN & if you UNPLUG ether1, it will use LTE
5. If using LTE and want that as a backup if starlink is down. set the a script= the /ip/dhcp-client for ether1 to add a ping check to the default gateway (so that if starlink gateway is not pingable, LTE will be used):
/ip dhcp-client set [find interface=ether1] add-default-route=no script=":if (\$bound=1) do={/ip route add check-gateway=ping comment=starlink gateway=\$\"gateway-address\"} else={/ip route remove [find comment=starlink]}"