I’m more thinking from a risk assessment standpoint than a functionality standpoint. I’ve seen “security questions” used as a backdoor form of authentication for 1, (as you mention) when you’ve forgotten your password or 2, phone conversations, typically with banks via the phone. In this case, a string of words is much more useful than the example you mention in your edit.
I guess I see your point here. You want to generate unique answers so that they can’t be guessed, right?
No; I want unique answers so if they’re stolen from site #1, they cannot be used at other sites. If the answer to “What was the name of your first dog?” is “2$V7x&8!ri!24z6$kqT9” at 100+ sites, then I’ve got a problem.
And because I’m generating unique answers per site, then I need an easy way to store them, and to have them automatically filled out in forms if it’s required, and to also audit “hey, you haven’t filled out your ‘security question’ fields - do you need to update them?” and similar risks.
So what I want is functionality that makes it as easy as passwords to generate, store, fill, and audit “security question” answers as passwords. Nobody would take seriously a modern password manager where you had to (say) open an app and tap 3 levels in to copy your password instead of having a browser extension just fill it in for you; likewise, I am hoping that “security question” functionality can be pushed to a similar level of ease.