I was in your situation some time ago. Good thing is that advanced (but little bloated, yes) harnesses have good enough defaults, so you don't have to go and read each setting before the use.

Regarding Pi my position is that it is brilliant piece of software if you don't need extensions - give the model bash tool and let it do all it wants through it or use Pi as SDK for your own advanced harness or smth similar.

But Pi with extensions has two problems. First one: rather often they don't play well together. For example, if you want some adjustments A and B for the same tool and there are two extensions which do A and B, they will likely not work as expected when installed simultaneously. You could say that it can be solved by adjusting extensions or just generating your own - yes and it is the second problem. Like any piece of code you own and use, you have to maintain it. Bug here, incompatibility there and voila - you spend your precious time to work on harness instead of doing your job. Plus remember that vibecoders are not very responsible people, so Pi extensions registry is flooded by "use Pi to customize Pi" buggy one shot extensions.

With carefully developed set of extensions Pi would be better, like properly configured Arch Linux could be better than Linux Mint in the hands of power user. But considering how fast things are changing in this sphere, seems it is more optimal to take more bloated harness - with unneeded tools, too big prompts, etc - which will be effective on 90%, but do the actual job with that harness right now.