I operate between Heathrow and Gatwick, so I know all about low level commercial aircraft, however these operate within strictly controlled zones/cta/tmas etc, and GA should be never busting that airspace, and if we did ATC would be routing traffic away from us. When we do get permission to fly in/through those zones it is via agreed limits/routes which do not impact on their traffic.
Any airfield within or under CTAs will also have set limits on their operations so conflicting with commercial traffic is nigh on impossible, and again, if you did somehow fly outside those limits and come into potential conflict, you wont need PAW to help you avoid that traffic, ATC will be doing that before you even know you have busted airspace.
Unless I am missing something?
Or lets put it another way, PAW is for GA to avoid conflicts with other GA traffic, not airliners, right?
Now, I accept that this may not be possible due to PAW simply detecting ADSB and not being able to determine whether that is a 787 or just a spamcan with ADSB enabled, but that is a different issue from GA traffic NEEDING to be warned about airliners operating in and out of our major airports. It is also something which Nav software can potentially do, based on track (into a major airport for example).
There may be other scenarios where a PAW user is in danger of conflicting with commercial traffic too, which I havent thought of, but even so, an option to turn off/on the traffic, if it were possible, would be an "enhancement" from my perspective.