View selectors states are appearing as configured in the analysis and hence stored in that objects XML definition. So basically not meant to be behaving in the way you are talking about in the context of GUI navigation.
You'll note that saved customizations take into account that specific GUI state of an analysis which currently has a different view-selector context. I've sapped together and example here: http://slc02ojw.oracle.com:7780/analytics/saw.dll?Dashboard&PortalPath=%2Fshared%2FOTN%2F_portal%2FView%20Selector&page=… (use Prodney / Admin123 ) to access.
So what you want is kind of supported by the engine in saved customizations, but since you can't call up an existing customization (like having one per view selector state for example) through a GoURL for example, your requirement can't be met.
Thank you very much for your answer. Unfortunately the page you did setup is not accessible from our network.
I thought first to build two view selectors. Each with a different default page. The other one would be hidden with css (display:none).
And how would the two view selectors with different default solve your issue?
With the different default it could show a different view first when I start the page...I hope