Good point Grant. I think the case could be made either way. An option in the XPRJ editor might be a nice solution.
Monarch does provide an indirect way to edit default state of a project by changing to that state, saving, and exiting the project.
Perhaps the driving issue is that it would be nice if Monarch didn't overwrite project settings set by Data Pump. But that may be very difficult to program.
But, I can see the value in being able to set the default view, sort order, and filter for a project explicitly. For a given complex model, a user may want it to open up the same default way every month. He will probably change the filter and sort order as he analyzes the report, and exit when finished. If any tweaks were made to the model, he will save them. If he wants the project to open to the same default view next month, he will need to make sure he returns to that default view before saving.
Just my two cents on the issue...