Rethinking the approach it seems easier to use only the controller to glue all information together and keep the razor view engine as is and do not add in a separate view engine for the above purpose.
The solution now has the markdown files within Content/Markdown/... and the controller maps and gets the markdown per request and returns the markup resulting from parsing it back into a view model which is then used to render in a typed view.