After reading all these posts tonight I have to say the "frustration" expressed by everyone is very real and very familar. I am in no way trying to mitgate the validity of the issues. Take my ideas as opinion. I have been an active Pro user since the late eighties and it has ALWAYS been the case, year after year, release after release, bug after bug, hit after hit, and miss after miss, these frustrations have existed with Pro.
In a nut shell, PTC listens but only when it's within their best interest. I like the idea of buying stock to vote out the special interest. However, remember PTC is a 30 year old company with preferred voting stock nowhere near us regular folks buying ability. That train has left the building. Sadly, my opinion is all your frustration is most likely falling on, not necessarily deaf, but indifferent ears. Hope is not lost though.
Having my PTC dance card for 26 years now, I believe it puts me in a postion to offer the following suggestions:
1. If you are able to have a Champion, a few Champions, a team of Champions in your respective organizations that are the Go-To people when people have questions...Do it. You will be better off for it. Pave the way for them to get trained to be Super-Users. Train as many as you can...as often as you can. Always be a learning organization. Do not rely on PTC or the Help line to give you the answers. 1989 was the last time I called 1-800-4PRO-HEL. In fact, I am not sure that is still the number. 
2. Have regular internal User Group meetings. Be informed, be open, share your challenges and better yet, do not withhold your stellar techniques from your team or company. You will not gain any special recognition for being stingy or exclusive. Get really good at being good and staying as good as you can be on your particular release with your particular product/processes. Find five or six ways to get to an answer.
3. Humbly I offer this....re-direct the time your are expending attempting to get PTC to listen to the gripes getting great at navigating the obvious landmines within the software. I know it ***** that the code has always been half baked and rife with counter-productive boondoggles. It's always been like this....and unfortunately it always will be so. Learn the work-arounds, don't cheat, don't hack your way through if you can avoid it. I can safely say in my 30 plus year career, on a dozen or so CAD programs, I have rarely found there was no solution to a problem. Granted, we deal with GUI stupidity, ribbons, retina burning white backgrounds, copy cat functionality and other CAD hype...stick with it as no software is perfect.
4. Engage an outside Trainer or Super User once a year to give you a critique. They will have the fresh un-biased eyes that will see things you may have missed. At the very least they will ask questions that will challenge your processes and methods in the same way ISO auditors do.
Hope I didn't Flame On too much.