Let me rephrase the question:
What are some benefits of having a single actionable event on screen (e.g. single child folder, single button occupying the whole screen estate, etc.), immediately followed by the user-induced activity (e.g. double clicking on a folder on Finder to see its contents, clicking on an actionable button in an application, etc.)?
To illustrate the question, I've taken an example from the file structure every OSX application seems to have:
Step #1: We're going to click on "Show Package Contents" to see the contents of "App Store.app".
Step #2: After the click, we realize there's only one folder, "Contents". This seems redundant, because the users most likely had decided to see the contents of "App Store.app" in Step #1 already.
Step #3: Here are the real "Contents" of the application.