I wouldn’t go so far as to say it’s literally the same as browsing a website. Your feed reader isn’t a full web browser and as far as I know most don’t execute javascript. They will still generally fetch images, and fetching the feed itself is just an http/s request, but it may or may not always be a request to the same web server as the website of whatever publication you’re subscribing to. So IMO you’re already starting from a somewhat better position in terms of data leakage, since the feed isn’t loading analytics software or advertiser javascript or any of that stuff which feeds the vast majority of bulk data collection in the private sector.

One downside might be that if you have your feed reader set up to automatically poll for updates regularly, you may forget and it may do that polling on networks you didn’t intend to (when your VPN is off or you’re on school/work internet).

If you have a specific threat model, or a couple, that you want to guard against, it’s much easier to come up with solutions that thwart those exact threats, than just trying to be “as private as possible” all the time (very difficult, all technical solutions have tradeoffs). You could make the requests through tor. You could use a proxy to encrypt your traffic up to a server you control before going out to the various sites. You could use a VPN service.

Those all have different tradeoffs: tor exit nodes might be widely blocked from fetching content from a lot of sites, and it might be hard to connect to tor period on some locked-down networks, the server host and their ISP can still see some details about your traffic if you run your own proxy or VPN server, but it is another step removed from your local network/isp and the site both tracking you directly by IP, user-agent, etc. VPN services might be tracking you themselves, might be working with governments, but they, similarly to proxies, interrupt the tracking done by your local network or the websites in question, with the added bonus of blending in with the traffic of other users (but they are often blocked by local network admins, and occasionally by websites as well)

As an aside, RSS-based podcasts are a place where this tends to get interesting since the field is dominated by big distribution services. Assuming HTTPS is in use, most podcasts you might subscribe to can’t easily be tracked by your ISP or network admins, since they’ll blend in with all the other traffic going to say, acast, libsyn, iheart, whatever, and HTTPS blocks them from seeing the full URL or data in transit, only the domain name from SNI. They can only tell that you downloaded data from a podcast network, not what podcast it was