Noel, that is an excellent illustration that a problem exists, but it needs more specifics. Were you able to identify specific registers that were flagged by the Registry Cleaners whose removal clearly led to the problem with specific WGA services?
A solid way prove the recklessness of using registry cleaners is to reproduce the problem, then make it go away by "undoing" the cleaner's deletion.[1] For example, back up the registers, then reproduce the problem by allowing the RC to selectively remove specific documented groups of RC-flagged registers. Next, show that restoring the same flagged registers makes the problem go away. You have now acquired irrefutable "smoking gun" facts.
You could then publish these "smoking-gun" examples that demonstrate the damage of a specific RC's actions. In fact, you might have a great article that shows how several different RC's do this kind of damage. I think this would be an excellent way to drive home the problem of registry cleaners. It would also turn the screws on the vendor to fix the problem.
Again, this would scientifically separate the facts from the hearsay warnings.
1. Roebear's excellent link (above) does this in an indirect way, but it needs to demonstrate Lolo's before-and-after damage by using it to show it clearly flagged and damaged these specific registers, which can be restored to make the problem go away. http://answers.microsoft.com/thread/f6fd8e12-e83a-457b-af0a-ae54a09b71b5