I've been testing this with the new beta patch. Leagues still come in with pitching still dominant but this can be "fixed" using league total modifiers. I simply import and create my universe. Sim a season and check the league totals compared to the target, I use the default setting
Code:
ootp default league totals
ab 167353
h 44522
2b 8919
3b 898
hr 5451
bb 16222
hbp 1850
k 31828
babip .297
results with all modifiers at 1.000
Code:
ab 165768
h 39133
2b 6265
3b 900
hr 4704
bb 8068
hbp 632
k 36583
Then figured percentages for increasing\decreasing totals to get what I wanted. Following table will have default league totals, modifier settings, and the results using those modifiers.
Code:
league totals modifiers results
ab 167353 none 168898
h 44522 1.121 45793
2b 8919 1.297 9264
3b 898 1.000 1053
hr 5451 1.137 5371
bb 16222 1.503 13132
hbp 1850 1.658 1137
k 31828 0.851 31865
At this point I am getting some fairly realistic numbers and could go one of two ways. Either call this good enough and play knowing some of the variation is simply caused because the game is ratings based. Or I could try tweaking one more time to refine the numbers. The only areas I would be concerned with this in my example might be decreasing triples, and hits very slightly while increasing walks.
IMHO I don't see this "pitching dominant" thing as a reason to not start a career. I play out every inning of every game in my dynasty and have since v4 while importing each year to the new version. I have always at least checked league totals at the end of every season and would estimate 50% of the time I do some tweaking between seasons. I do this without simming out a year to see how things will work. I only do the season sim with 2006 as there is a big difference that needs adjusting when you import.
Whether this should be considered a bug or not I don't know. I do know that through league total modifiers it can be fixed.
The only thing that should hold you back on starting a dynasty is the wp, balk, hbp, and hb ratings not importing bug. This is definatly fixed in the upcoming patch. A "work in progress" patch should be coming July 7th that, as I understand it, will include this fix. So if I were you I'd wait 'til Friday to give it a go.
Hope this helps.