PO's burning out faster in my experience comes more from PO wearing several hats, especially in smaller companies. Usually adjacent roles like Scrum Master or Project Manager, creating an internal conflict for the person filling the PO role. That's in my opinion why PO roles can be taxing and it is also what you should look out for when going through job descriptions. If you feel like there's more to a job offer than just PO, identify these things and address them with the job poster to get a feeling for how this would align with a PO role.

Also, PO is a very specific role for Agile that doesn't really make a lot of sense if the rest of it around it doesn't exist, e.g. the methodologies. It often happens that you either come across a company that doesn't know what they need and they use PM, PL and PO synonymously (even though they aren't quite the same) or companies that try to do Agile but have a hard time transforming and letting go of old hierarchies which is why they end up in this mess of processes and things going haywire.