I GOT IT!
I figured out the issues with P-States! I'll need other to corroborate it but I got it!
In the case of ASUS boards you have 3 options for AI Overclock, Auto, X.M.P, and Manual.
Each cause OSX to behave differently, which is not what you expect by any stretch. I'll explain each!
Auto-Auto
P-States work exactly as they should, there is full amount of P-States, and they throttle between 16-38. This is proper operation. P-States reached 16 17 19 20 21 31 33 34 35 36 37 38.
Auto-All Core
This causes the P-States in OSX to go hay-wire. Such as when I was getting only 16 17 19 20 21 38.
Auto-Per Core Auto
This causes the P-States in OSX to go hay-wire. Such as when I was getting only 16 17 19 20 21 38.
X.M.P
You'll likely choose XMP to enable your 1600 mhz of your DDR3 ram. This causes the P-States in OSX to go hay-wire. Such as when I was getting only 16 17 19 20 21 38.
Manual
Same as the non-auto states/auto
So basically unless your full auto for anything CPU related you don't get all the P-States. I've heard people mention of an option for P-states but it's nowhere to be seen.
Any ideas if you can set these P-states manually in the DSDT? As this explains why when was on test bench/table before my desk (with 4gb's of 1333mhz ram) everything was super...!
P.S.
Is it safe to flash between the patched and unlatched version of the same rom? I'd like to see if it is a side effect of the patch or if speed stepper and un-patched work in any mode as it should...
Update 5/2/2012:
Seems that the major issue is the SSDT table that is being generated is bogus, it only will work if 100% stock ASUS settings essentially. Even if you put ram at 1600 mhz your SOL. I'm researching how to edit/create an SSDT table and possibly a guide (but it seems complicated) as it is definitely something that needs to be done on a system by system basis. Though using RevoGirl's RevoBoot might work no issue–I just can't figure out how to compile it, trying though never use Xcode much -_-