As a technical founder, I agree with you to a degree, but not completely. I've come to appreciate sharp, non-technical founders with business acumen and who can see the "forest for the trees". There are times where being "technical" is actually a crutch, because you're more likely to:
1. Waste time / obsess over small technical details that in the grand scheme of things don't really matter, or at the very least, don't matter until you have validated product market fit. These details can be anything, from the design or shape of a button, or the perfect fully-normalized schema for your database or whatever.
2. You over-engineer technical solutions, like building a homegrown SaaS app or fleshing out a database for something that should have been validated inside of Google Sheets or email.
3. Idea generation - because they are non-technical, they often see potential products where technical people won’t because the technical person overestimates the amount that a non-technical person will commit to solving a problem. If you asked a technical person how to do XYZ, they might say something like, "oh that's easy, just set up a ABC server and VPN into it and run this bash script and blah blah blah". A sharp non-technical founder would immediately sense that to the average person this is absurd, and thus a potential product opportunity. I see this particular bias all the time on Hacker News.