CF terminated TLS and scans the traffic. It makes sense if you host your services on a VPS.

If I run my services at home, I don’t want to provide Cloudflare with access to my data.

It also makes sense if you run public services at home

Public in the sense that the actual content is public (like a blog), sure, anyone can access it, so does the reverse proxy). Since it’s public, I Would still take the trouble entirely out to a provider.

Public in the sense that the front page is public, and the client still need to authenticate to the service at home, in this case, that does not make sense (the user authenticates to reverse proxy, which authenticates to the service), for the reason I mentioned.