On the topic of whether an exploit that allows homebrew should also have protection against use for piracy, my stance is very simple:
As long as it doesn't take much development resources to implement protection, it's OK. However, if more time is spent on implementing protection and maintaining it than polishing and maintaining the actual exploit itself, it's NOT OK.
Additionally, I'd prefer piracy protection to be kept simple such that if someone wants to use the exploit for piracy (and this will happen no matter what protection is implemented) the developers involved in maintaining the exploit don't take it necessary to patch any such workarounds that might become public knowledge.
Let's face it, like fail0verflow said, homebrew used to be much more interesting because it enabled functions in a console at a time when such functions weren't widespread and easily available. For all intents and purposes if you truly wish to develop homebrew, a better way to spend time would be to fiddle with a Raspberry Pi than a Wii U. I'm personally waiting for homebrew on Wii U for one reason alone and that's to ditch the Wii U GamePad for good. If we'll have a kernel exploit, I want to believe it should then be possible to have the Wii U Pro Controller simulate a Wii U GamePad, either using a shim or modifying existing IOSUs that handle controller input. Either way it's something I'm personally looking forward to if someone is working on a project like that.