If the goal of stack* sites are to become a FAQ; why not to allow an user to be able to post tutorials and associate a list of possible questions to it?
When a question gets asked many, many times, we will often ask a users to create an awesome, canonical answer so that all the numerous duplicate questions can finally, once and for all, be referred to the one canonical answer.
But posting a tutorial is a bit awkward in this Q&A format. I don't think it will go over that well, in and of itself. Perhaps it would be better to provide the best possible answer to the question; if that included also linking to a tutorial appearing elsewhere on the web, that would be kindly regarded as all the more helpful. But the answer should reside in the text of the message.
As for "faking" a question as an excuse for posting something; it is certainly allowed, but how it is received depends on the context. If you have a helpful answer to a problem you have actually faced, it might be seen as helpful. But if you were to create a tutorial and forced a question to point to it, that could be construed more along the lines of spam and might not be received as well. The guideline I would use is to make sure the content is very organic to the site. It's best to wait for the occasion of answering an actual question, but failing that opportunity, make sure your faked question part of a long line of otherwise useful contributions to the site.
One downside of tutorials is that they take a lot of space so other answers can't be seen. It is just as useful to post a tutorial on a blog and link to it where relevant.
Also tutorials are more general and often not suited to specific questions. If it is a relevant answer to a question then I don't see why it wouldn't be allowed.