CRS - broadcast storm ( loop ) protection

I have CRS226 (RouterOS v6.35) set to default configuration (ether1 is master port of all other ports) and I would like to prevent it from loops (in case somebody accidentally makes physical loop between two ports on a switch).
I know that this is trivial at SwitchOS, and there are two approaches at RoutrerOS:
-to put all ethernet ports in bridge and turn RSTP on
-interface->ethernet-> switch->ingress-port-policer

I think that first approach is not suitable for CRS because bridging of interface is wasting of resources on CRS.

I’ve tried second approach with ingress-port-policier, without success. I’ve found and tested a two MikroTik CRS examples:
/interface ethernet switch ingress-port-policer
add port=ether$ rate=500 meter-unit=packet packet-types=broadcast

and
/interface ethernet switch ingress-port-policer
add port=ether$ rate=5k meter-unit=packet packet-types=broadcast,arp-or-nd,unregistered-multicast
( ether$ means that I have added a role for every port I’ve used in test )
and nothing happens, still losing a switch in case I made loop between two ports. Is it because there are no VLANs configured (except automatically created VLAN 4095 on switch1-cpu) and there is no any Ingress VLAN Translation role defined (except for 4095)?


I emphasize that I want CRS (226 or 125) to be configured just as simple switch. Is there any suitable solution for loop protection in this configuration?


Thanks!