I don’t think the thing about Safari naming tracks at all. Keep in mind that Safari has existed since 2003, during which Apple was in a very different place — back then there was no App Store or even any hint that such a thing might exist at some point and OS X was going all-in on open standards compliance, with things like RSS support being major touted features, and WebKit was quickly approaching Gecko in being a top class web engine (as opposed to the dominant Trident and Tasman in IE and IE for Mac, respectively).
As for in-app webviews, they’re not all made equally. Most apps use SFSafariViewController, which is an out-of-process Safari tab with its own app-specific cookies, local storage, etc that’s designed to give the user an opportunity to see if the page is really something they want to access and helps keeps their main browser’s tabs clean while also breaking several types of trackers. Of course though some notoriously nosy players like Facebook and TikTok don’t use this and instead implement their own which is chock full of tracking crap… this is probably an area where Apple could stand to be more heavyhanded (ban custom browser reimplementations except where those add demonstrable value or the app itself is a browser).
Also, web app devs aren’t blameless in user preference for native apps. For every web app done right, there’s three more that are shoddy and frustrating in ways that native apps generally aren’t (think breaking back button, scrolljacking, etc), some that are just plain badly built, and many that are unrepentant resource hogs. Often this applies even to web apps that have no counterpart native apps because their companies chose the web solely because it’s cheap to do so (resulting in cheap bad web apps). Are there crappy native apps too? Sure, but they’re somewhat less common and generally keep the crappiness somewhat bounded.