Bill, thanks for summarizing this info, but I think there's too many unknown factors to support this conclusion.
The connectivity issues that I'm referring to, and awfully similar to what Sid has mentioned, involves mostly desktop / laptop / streaming TV settop box type clients after *days* of uptime. In Sean's environment (stadium/convention center), it's very unlikely that there are any of these types of clients, and it's even less likely that any particular client hangs around for that long. Plus, their users are unlikely to complain about momentary connectivity issues, and probably just shrug it off and toggle wifi. I was at Levi's Stadium not too long ago, and their wifi (I believe Aruba based) kicked me off to LTE every few minutes. I never complained, I just grumbled and went into Settings and reconnected every time I wanted to use my phone. You have to wonder how much that happens in a stadium style deployment.
I don't think a minrate of 24 or an aggressive roam factor of 4 is a good idea for most deployments, unless you are truly aiming for high density / max throughput at any cost. I can guarantee you that for streaming video or VOIP clients or folks using smartphones while walking around, using either setting recommended above virtually guarantees clients will be kicked off the wifi network briefly, which can be very annoying for VOIP / streaming.