I benchmark most interpreted language http frameworks in the low tens to hundreds of requests per minute range at best without any app code and you're telling me that CPU performance isn't an issue?
No, I'm telling you that CPU performance usually isn't an issue. Most sites will never, ever need to serve enough dynamic requests for that kind of performance to be an issue (and you can certainly do far better than that on dirt cheap hardware).
There are certainly types of code that will be CPU bound, in which case, yeah, there's a good case for using something else - or calling out to something else -, but for large parts of what people write, not being IO bound is a warning sign that you should take a long hard look at what you're doing, because chances are you're doing something silly.
Webapps and typical APIs for webapps tends to be amongst those.
Of the work I've done in the last 20 years, maybe 2-3 projects have been projects where CPU performance have been an issue. For others it will be every project they every do. But the point is there are plenty of us for whom language performance is not a factor we usually need consider.