Yes, that is correct. That is all we have done in this area. It is now an explicit action to bring along styles from another application.
As alluded to in my previous post, we have not yet revealed everything about version 5. I can tell you what we've release in the public builds so far and comment on somethings that we are fairly certain we are not doing at this point for the 5.0 release. For some of the people frustrated with styles, we may have something to help them. However directly addressing the issue of overriding text styles is one thing we are not doing for 5.0. There has been much talk about it though and the new file format will allow us to make changes in an update without creating files that are completely incompatible with earlier versions of v5.^
I have explained in previous posts of this thread why it works like it does but if you would like more examples or details I would be happy to give them. OmniOutliner styles are a very polarizing issue so we need to do our best to not just swap one camp for another. So as a first step we are trying to help people avoid putting themselves into the situation in the first place of having text styles they didn't want.
^ The last time we made major changes to the style system was with the 1.0 iOS release and it just created a massive cross-platform issue as we were hitting limitation of working with the same file format. Ultimately, overall the changes were a failure on its own anyways so they were never released on OS X.