As we explained in your original question, the node to which this traffic should be flowing MUST send a frame for the connected switch to learn its location. And it must be a broadcast frame if you want the entire network to learn it. For IPv4, ARP takes care of this; IPv6 NDP. A gratuitous arp from a switch will only get the traffic to that switch, but not necessarily the correct port.
While, yes, flooding does naturally occur in switched networks ("fabrics"), it's a rare event that doesn't last for more than a few frames. The ARP process will usually fill the switch tables, and re-verification will keep it filled. If you doubt how little traffic is actually flooding, go to any node on any switch in your network -- preferably one in a VLAN with many other nodes -- and start a promiscuous tcpdump filtering out the local MAC and all broadcast traffic. There will be very little "foreign" traffic showing up.
This kind of unicast flooding is Very Bad(tm). It is effectively a broadcast storm, but because it's not actually broadcast traffic, the switches cannot detect and block it like a real broadcast storm. If it's only 10pps, then it's much less of a catastrophe. But when it's a significant amount of traffic, it becomes a huge problem because every port in the entire network (carrying that VLAN) will have to carry the traffic. Yes, your NIC will filter it out, but it still consumed bandwidth crossing the link. (your NIC received it, but didn't pass it on to you.) Do you want every node in the network eating 800mbps of traffic it doesn't want?
