I've flashed freshly compiled build with latest commits (kernel 6.1.46).
For me the issue is still there absolutely repeatable when multi to unicast
is not checked.
The "workaround" option multicast_to_unicast_all '1'
only masks the issue temporary but at one point it doesn't matter at all.
I'll continue to monitor how it goes/changes as time goes by.
Update - reading this post.
I can confirm this behaviour too with today snapshot and obviously multi to unicast
is not even a workaround for the above issues.