If taken from the context that the un-technical co-founder will be conceptualizing, if not creating, the product UI itself, then yes, by all means, this person should get out of their comfort zone and gather as much knowledge and learn as many toolsets as they can and in order to at least be able to transfer their ideas into a visual system of sorts until someone with the appropriate expertise comes around and implements their vision.

Depending on the level of investment that a company is putting into their UX, then maybe this approach makes sense if you're going to be trolling the Craigslists looking for a student who needs to pimp out their portfolio in exchange for a hot meal, but in all seriousness, treating UX like some low-hanging fruit that a business person is going to pick up after a couple of Frontpage tutorials is ludicrous, not to mention downright insulting to anyone who practices the craft. I believe the same applies to anyone who works in the middle-tier or back-end. If the non-technical co-founder is smart enough to partner themselves with a technical person whom they can trust to make the right technical decisions while sharing responsibility for the costs, then they won't need to be poking around in the details trying to micromanage something they have no inkling of understanding, never mind actually designing, developing, deploying, maintaining, troubleshooting or fixing should everything go south.

I'll go back to my original premise: learn to communicate well in English, both in spoken and written form.

A person who can master that will be at an advantage of selling the company's product, services or team to any client, partner, potential employee or investor over someone who cannot speak publicly, has grammar issues and spends their time fucking around with powerpoint-related technologies. Effective communication starts with language, not toolsets, in my most humble opinion.