Well, I never expected Pipewire would replace Jack. I always assumed one would just continue using Jack for low latency audio and let Pipewire replace pulse. If it's possible for Pipewire to equal Jack's performance that would be fine.
I have recently installed Pipewire on a machine I use for ham radio. The ham radio apps use pulse however there is a need for audio to be routed between apps and some microphone signal chain inserted. I tried doing it all in pulse with either pulse effects or running Carla with a pulse engine and the results were dismal. Switching to Pipewire everything works very much like it's all running in Jack as far as routing goes. Every Pulse app presents ins and outs just like a Jack app. Carla can run using a Jack engine and doesn't seem to notice it's actually running on Pipewire. Easy to get it all routed in qpwgraph. I can get latency down to about 16ms setting without issue. It's low enough that everything works fine and since I don't have to monitor my mic in the headphones it's fine. Over all I quite like it. However, playing guitar through Guitarix at 16ms latency would not make me happy. I need to monitor that live. This is where I use Jack set to 5ms.