I've seen GitHub take five seconds to render a 100K line diff. In my experience all of the other tools I've used, including some of the ones listed, can take longer to render individual file sections of such a diff. It's fast enough.
Comments are sent as they are written; you cannot "draft" comments.
I'm a bit puzzled as to why you would need to draft comments inside the PR interface, especially in light of the fact that they can be edited.
Cannot compare differences between patch sets.
You most certainly can. Just use branch/revision compare.
To create a patch one must fork the repository publicly (weird and unnecessary).
Also immaterial.
Accepting a patch creates a "merge commit" (ugly repo history).
This comes closest to being a legitimate complaint. Because GitHub emphasizes recognition of contributors, it doesn't let you rewrite the commits in the PR as you merge them with the merge button, but there are multiple ways to merge on the command line that avoid the merge commit and play nice with the PR.
In general, pull request culture is not about code review.
WTF?
Sounds like a strong case of NIH.