An HDD MBP will obviously beat an SSD rMBP in graphics rendering since it's rendering almost 4 times less many pixels with the same GPU. So that's not an issue at all. If you play a game in a regular and retina MBP, the gaming performance is the same as long as you play it at the same resolution. So there are no graphics related bugs in retina MBP's. And SSD/HDD have no effect on GPU performance. About slow shutdown times, I think it's effecting all macs, not just SSD ones, and that's not really an issue that needs fixing immediately. There are a lot more important things before we come to that.
About the number of open tickets, for every release of OS X, there are thousands of open bug tickets at all times. And that is quite normal.
Good points about the graphics. My only contention is (in theory) a retina product should not have been released with so much [seemingly] left to "flesh out". Meaning, the numerous hardware and software issues that many have been experiencing should not have happened to the extent it has for such a premium product that Apple seems to have been pushing as "the next best thing". A MacBook Pro should not out-perform a retina system, if it does than there is an underlying issue. Certainly a rMBP has more work in graphics rendering, however paying a higher premium for slower graphics with a myriad of glitches in Safari and over core app's should not be outweighed by the factor that it is a "retina" display. Work out the kinks, then release the product. Hopefully the next releases will be much more stable and consistent (a byproduct of first batch systems perhaps). What about OpenGL Core 4.0 support? It's god awful, something OS X has seemed to be suffering from for a while now. Windows systems blow even the most supped up Mac's out of the water. It's shameful. Releasing a "retina" display with shoddy graphics cards, resulting in over heating systems, shutdowns, graphic glitches. It's as though Apple focused more on the display and less on proper hardware support to drive it.
As for tickets, I have experienced WiFi issues on my current gen 12-Core Mac Pro, 2012 MacBook Air and 2011 iMac. All systems have clean installs of 10.6.8, 10.8.2 and 10.8.3. Snow Leopard experiences no WiFi connectivity issues (dropping, spikes, inconsistent signals, etc). All things remaining equal, 10.8.x has definitely suffered from WiFi instability, running the latest .3 update doesn't seem to be helping. I've run this on guest accounts, clean installs using the buried .dmg on a USB drive, etc. Many user forums are frustrated by this issue. Personally, I found the networking protocols (I'm talking about you SAMBA) that Apple utilized in 10.7+ to be a huge hassle, especially for server related instances. I'm glad that finally got worked out, perhaps Apple jumped the gun in updating certain aspects, breaking compatibility, who knows. Safari has certainly improved, caching issues with websites not updated were a major PITA having to reload any time you navigate.
One aspect I'm on the fence about concerns the social networking features throughout 10.7-8 which seemed to be a major focus for OS X software engineers. I personally don't need them, but I've read numerous debates regarding the "bloatware" of said features. Some state it doesn't effect system performance if they are not configured/utilized, and others have shown proof that even unused they eat up background resources (which is rather perplexing).
10.7's Memory management was atrocious, 10.8 has been slightly better, however they fall well behind 10.6 in terms of overall functionality, speed, and stability. A system in 10.6.8 with half the RAM generally runs faster than a 10.7-8 system with double the RAM (and I'm not including the rMBP's in this remark). Why? What is the need for so much memory in a base system? I installed 10.8 on a friends 2010 MacBook Pro with 4GB's of RAM (from 10.6). It's so slow, simply using Mail, Safari, iTunes and smaller non-core app's is god awful. She went back to 10.6.8 and it's a breath of fresh air. I really wish Apple released a .9 update for Snow Leopard with iCloud integration, it wouldn't have taken much engineering wise and those who refuse to migrate would be able to purchase and use iDevices with their iCloud accounts. I spent about a month reading online forums on how to configure iCal, Mail and Contacts with iCloud in 10.6.8, Contacts being the bugger. Finally got it working perfectly, although it still doesn't have the full iCloud compatibility offered in 10.7+. When 10.7 was released, 10.6 systems were hardly legacy, yet Apple refused to simply update key features in order to push out new Mac's and 10.7 (which was the first time Apple departed from ISO ~ bi-weekly beta testing for an average 4 DP's before GM, and while OS X 10 was most definitely a terrible release, 10.7 was nipping at its heels).
It seems 10.8.3 is making its way as the longest and most released OS X 10.x.x release to date. Simply stating that there are "no known issues" doesn't mean it's issue free, there are plenty of open bugs that I have received follow-up's directly from Apple engineers requesting screen caps, movies, and detailed information. If Apple cannot get 10.8.3 ironed out, how is moving to 10.9 this year making any sense? You cannot build upon a core OS that needs work. Certainly 10.9 may be a complete rewrite, who knows at this point, but if it is anything akin to 10.7 and 10.8, I fear it may be a bugged disappointment.