Exact same boat here. We're dependent on the BD firewall, and it doesn't have the ability to filter broadcast traffic (according to them, this is due to a bug with the Windows Filtering Platform, not a decision on their part). The registry trick has greatly reduced how often people start the broadcast, but it still happens without fail when printing from certain applications (photos.exe, snipping tool, etc.). Our only recourse at the moment is watching for the traffic in wireshark 24/7 and manually killing dashost.exe as soon as someone starts being problematic (or scripting the same steps). It's truly heinous and all we can do is angrily await a new build that hopefully fixes the issue.
We're in the same, 120 computers and as they've been updated, it's become unsustainable, I have logged 4 broadcasts per second per computer, network stability is clearly in danger, It's incredible that Microsoft hasn't fixed this!
We've disabled the device association service and the broadcasts disappear, but programs that use native Windows printing fail or take forever (Notepad, Paint, Photos...)
We use BitDefender Firewall instead of the Windows one, and not permit drop broadcast...
Any other suggestion?