the argument isn't why use a PWA, it's why use a native app?

in most cases, a team wants their product to be easily installable, live on the home screen, and have access to all native APIs. right now, the best way to do that is a native app

the cost to that is going through the app store, meaning paying apple for the dev license, paying apple a percentage of sales, adhering to the app store rules, allowing extra time before release to get apple approval, difficulty updating because you need apple's approval and the user to update it, needing apple hardware, separate codebase/dev skills for android/ios, etc.

if you don't need those pros above, you could maybe get away with a PWA, and avoid all of that hassle. in most cases, you can't, but avoiding all of that stuff is the value prop for a pwa

If you only want to target one platform, and if you are already completely set up for native development for that platform, then yes, there's nothing to gain from going PWA instead of native.

Other than the learning experience of course, which you might consider valuable unless know for sure that all your future projects will remain on that one single platform.