I'd create two separate business objects each with their own data environments. If the second view is a child object of the main business object and is designated as such, then it will be updated if you've marked to to be saved when the parent is saved.
What I don't understand is why there would be a problem with the second/child view being requeried whenever the parent changes. I've never noticed a performance loss with any forms that I've done and some of them have a many as 4 -6 child business objects.

If the second view is not a child or doesn't need to be requeried automatically but only on demand there's no problem doing that either with this scenerio of separate business objects and DE's.

I did some one-on-one with Kevin earlier this year and the understanding that I took away from that was that keeping one view per BizObj and DE was the way to go - especially if the app would ever be transported in whole or in part to a web app.