What is "par" here?

Nobody was complaining about the Switch CPU. It was a pretty solid choice for the time. It outperformed the Xbox 360 somewhat, which is really all it needed to do to support last-gen ports. Like I said, the big annoyance that was specifically CPU-related from a dev perspective was the low thread count, which made cramming previous-gen multithreaded stuff into a fraction of the threads a bit of a mess.

The point of a console CPU is to run games, it's not raw compute. The Switch had what it needed for the scope of games it was running. On a handheld you also want it to be power efficient, which it was. In fact, the Switch didn't overclock the CPU on docked, just the GPU. Because it didn't need it. And we now know it did have some headroom to run faster, jailbroken Switches can be reliably clocked up a fair amount. Nintendo locked it that low because they found it was the right balance of power consumption and speed to support the rest of the components.

Memory bandwidth ended up being much more of a bottleneck on it. For a lot of the games you wanted to make on a Switch the CPU was not the limit you were bumping into. The memory and the GPU were more likely to be slowing you down before CPU cycles did.