Even with GPLv2, adding additional restrictions effectively creates a new license -- one that is incompatible with the original GNU GPL, and for which GNU/FSF will not permit you to use the GNU GPL name or preamble. (This is covered in the GPL FAQ.)
This is not surprising, since the sorts of restrictions mentioned in this thread violate "freedom 0" of the Free Software Definition.
A copyright owner can always release the same software under a different license. They just can't call it or expand upon the gplv3 license itself.
So when the GPLv2 says that "You may not impose...", that only applies to someone who is re-distributing the work, not to the original distributer.
The GPLv3 is different, due to section 7, since the licenser can't remove that line (the GPL itself is not Free to modify).