Something like Awake that runs even if disabled?

The documentation for Start says:

Like the Awake function, Start is called exactly once in the lifetime of the script. However, Awake is called when the script object is initialised, regardless of whether or not the script is enabled. Start may not be called on the same frame as Awake if the script is not enabled at initialisation time. http://docs.unity3d.com/ScriptReference/MonoBehaviour.Start.html

It always seemed to me like Awake would be called regardless of whether an object were enabled or not, whereas Start would be called only when the object became active. And that this would apply to app startup. But that does not appear to be the case.

http://forum.unity3d.com/threads/unityevent-disabled-objects-awake-failure.267241/

My question is whether there is anything like Awake that is called even on disabled objects when the app is started. Because that would be terribly handy. (Or am I misunderstanding Awake, maybe it does somehow run on disabled objects at startup?)

So I think I do understand the difference between Awake and Start. If you Instantiate an object then disable it, Awake will run but Start will not. So you should initialize the object itself in Awake and its connections in Start.

What I'm asking is why can't there be another callback, like Init, which runs only at app startup, for all disabled objects in the scene, if it exists. Unity could make a list of which ones to call when it builds the scene, so it doesn't have to traverse the scene hierarchy at startup. (This is basically how static initialization functions are compiled in some languages.)

At the very least I think the docs should be clearer that Awake is not called at startup if the object is not enabled, because it really seems like it would be, as the docs currently describe.