You don't seem to explain any reason for using CloudFlare on top of GitHub pages. Care to elaborate?
Yea, nowadays GitHub Pages supports HTTPS with custom domains: blog.github.com/2018-05-01-github-...
DNS is really irrelevant to GitHub - you can handle it anywhere. I generally use e.g. Google Cloud Platform/Azure/AWS's DNS capabilities as they're super cheap and convenient.
And a CDN is probably not going to make a massive difference to your GitHub Pages -website - not sure what you're hosting though hehe.
Anyway, interesting to hear your reasoning.
You're right for most of the above points, I like cloudflare to do almost application level stuff (eg. domain redirect codewithhugo.com/the-step-by-step-...) and to be able to set caching policy for assets (GH pages doesn't allow that).
It's not crucial but it's been quite useful to get some stuff done.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.