No because you can't run a scenario or scenario damage calculation by giving in input an hazard calculation. However, not all the cases are covered by this ugly function. Consider for example this bug (https://bugs.launchpad.net/oq-engine/+bug/1169886).

The solution, I am going to implement in another pull request, is to get rid of this complex logic and avoid getting the metadata from the ```Output``` object that is opaque. Instead I want to follow the approach described here https://bugs.launchpad.net/oq-engine/+bug/1169541