The lead dev on this feature, who also wrote the blog post, is taking some well deserved r&r after getting this feature out the door. I was somewhat tangentially involved (I work on the Shadow simulator, which we used to test, evaluate, and tune this feature) but can take a stab at answering questions.
Otoh comments on the blog post itself are likely to be seen by more experienced tor devs than myself :)
Slightly off-topic but do you have any pointer for someone who would like to help optimizing Tor? The current documents portal [1] has a big "OUTDATED" banner attached, and the WIP new portal contains too little information for me to make sense of how Tor works internally.
I worked on some areas of TBB before, but still feel like I don't know enough about Tor's internal.
[1]: https://2019.www.torproject.org/docs/documentation#DesignDoc
As always it's probably a good idea to reach out to chat about what you have in mind before getting too far with implementation. #tor-dev on OFTC IRC (bridged to Matrix)
https://www.torproject.org/contact/ https://blog.torproject.org/entering-the-matrix/
How well would the new congestion controls be able to handle udp traffic from aggressively opportunistic protocols like bittorrent over UDP, assuming that datagram traffic is allowed on the tor network?
As far as I know, bittorrent's udp congestion control assumes the network is able to drop packets and clients definitely act accordingly.