M4300 IGMP Snooping and Report Flood Mode

In an AV network with multicast streams, I have an M4300 switch which has IGMP snooping enabled. Multiple hosts connected to that switch joined the multicast group 239.1.1.1 and sent their initial unsolicited membership report, which made them receive traffic in the first place. However, multicast would stop flowing for some of them after about 30 minutes.

What I noticed is that all hosts see the IGMP membership reports of all other hosts on different ports of the switch due to the "report flood mode" setting being enabled, which makes them seize to send their own reports.

RFC1112 yields this:

If a host hears a
Report for a group to which it belongs on that network, the
host stops its own timer for that group and does not generate
a Report for that group.  Thus, in the normal case, only one
Report will be generated for each group present on the
network, by the member host whose delay timer expires first.
Note that the multicast routers receive all IP multicast
datagrams, and therefore need not be addressed explicitly.

Linux implements this correctly.

This eventually makes the switch stop sending multicast frames on the ports it didn't receive reports on.

Because of this, RFC4541 states in section 2.1.1:

A snooping switch should forward IGMP Membership Reports only to
those ports where multicast routers are attached.

Alternatively stated: a snooping switch should not forward IGMP
Membership Reports to ports on which only hosts are attached.  An
administrative control may be provided to override this
restriction, allowing the report messages to be flooded to other
ports.

Which is what the switch is doing, but only with the "report flood mode" setting disabled.

I wonder what the purpose of this setting is, and why on earth it is enabled by default as it breaks all RFC compliant multicast implementations.