This framing is neither helpful nor accurate. The discussions of multiple trailing closures were exhausting for the community, with many hundreds of messages in the review and pitch threads. You cannot get an accurate read on support for a counter-proposal from that much signal. I am concerned that the relatively low volume of feedback on SE-0286 is a symptom of, effectively, collective burnout on this topic.
The Core Team has said they are not going to bring the optional-first-trailing-closure proposal up for a review now. It is time to go and use Swift 5.3, with SE-0279 and maybe also SE-0286, to learn where the remaining problems lie. The base state is no longer pre-SE-0279 Swift, but SE-0279 + (maybe) SE-0286, and that is not something that is fully understood as yet.