Wireplumber policies worse than pipewire-media-session

Recently my system switched to wireplumber, but wireplumber seems to be a significant regression in policy choices compared to pipewire-media-session.

On my system, bluetooth is never selected when connected. Bluetooth headphones default to headset profiles. Microphone loopback interface is prioritized above soundcards for output.

I'm not sure if this is considered a bug in wireplumber but for users its quite annoying to have to go back to the dark age of configuring my audio like in pulse when pipewire-media-session "just worked".