Do not use handover triggers. That is a legacy construct and should not be used.
Do not change any client match settings. The power of your access points is the main determining factor of how clients roam, if they hold on too long or if they try to roam while they are just "sitting there".
Client Match operates after a client has already made a decision to roam, minimum 2 minutes after it is already on an access point. It is not a roaming mechanism. Setting the power of your access points correctly allows them to roam better, so you do not have to consider tuning clientmatch to do anything after.
Devices set to "unsupported" means that clientmatch tried three times in a row to steer them and they did not respond. "unsupported" means that client match will not act on those devices for another 2 days by default. Again, setting the power on your access points means that (1) they will choose the correct band (2) they will roam more easily and (3) Clientmatch will not have to "clean up" clients that have roamed poorly.
If you are setting the ARM-MAX-TX power in your access points to above 18, you are doing it wrong. Asymetric power between your clients and the access points is the biggest cause of sticky clients, lost data due to one-sided connections and clients roaming randomly and disconnecting, because the power is too high. Having the power greater than 18 can also cause a great deal of co-channel interference which punishes your wireless performance.
If you are setting the 2.4ghz ARM TX power equal to, or more than the 5ghz, you are doing it wrong; The 2.4ghz band travels further and needs to be less than the 5ghz tx power by at least 3db for clients to want to go to 5ghz instead.
If the difference between your max tx power and min tx power is more than 6, you are doing it wrong; db is logarithmic, so every 3 db increased or decreased is a doubling or halving of radio power, which can be considerable. Making the difference between the min and max no more than 6 makes cells more even and roaming more even.
If you are running 80mhz channels, with any type of density, you are doing it wrong; There are not enough non-overlapping 80mhz channels to not cause interference. In addition, no all clients even support 80mhz channels, so you are wasting bandwidth. Go to 40 mhz channels or even 20 mhz channels. It will give you more non-overlapping channels to deploy.
If you are not dropping broadcasts and multicast at the Virtual AP level, you are doing it wrong. Multicast and Broadcast traffic are the sworn enemy of wireless traffic. There is very little if any mission-critical broadcast or multicast applications that are run on wireless.
If you are having problems, you should open a TAC case to get their opinion, or even hire a professional reseller to help you plan your network properly. I frequently see many of the same people with similar complaints that are totally solvable or that can be lessened with a little help from TAC or professional help.
We can answer some questions on here, but someone needs to advise users of the "big picture" specific to their environments. I can imagine alot of users on here see an idea that they like and it gets applied out of context or without taking the big picture into account. That can hurt more than help.