This looks unfeasible, even with patents. Patents are meant to tell people explicitly how to do certain stuff with the condition that if you sell/make money with what you do with that method, you're supposed to give a cut to the patent holder.
That's the theory.
The pricing strategy and the "patenting the obvious over and over again" practice, then, get in the way of the OSS and business in general, but teaching should never be hindered and constrained by this kind of matters.
Now... a case that might fall into a gray area is that in which your teaching steps on the toes of the big, bad, evil, armed to the teeth, hardware/sysadmin certification business.
Those guys try to boss out competition by:
perpetually changing/adding to the APIs / GUIs / CLIs, they have access to,
pushing hard on their trademarks, making it practically illegal for competitors to advertise what they're trying to teach,
bundling certifications with products and product discounts with certifications,
pursuing a crazy education style, obsessive over the nit-picky details,
discrediting traditional, sane, top-down, approaches to education.
Then again, as always, IANAL. Be warned.