There is a blog posting describing how to remove obsolete contracts from the WSDL:
Does this meet your requirements?
At this point of time we support exception marshaling through fault contracts.
Can you please clarify and provide an example/sample of what additional scenarios are needed for WCF VNext?
Unfortunately, implementing this suggestion would result in a breaking change. At this point of time, WCF does not plan to investigate this ask. Please let us know if there are further concerns.
At this point of time, using NET.Pipe is the recommended approach for WCF in-process communications. We do not plan to support local binding for the future.
At this point of time there are several 3rd party Nuget packages released that accomplish WCF dependency injection where no default constructors are required (such as Ninject.Extensions.Wcf, Unity.WCF, Autofac.WCF, Castle.WcfIntegrationFacility, etc). There are no plans for WCF to incorporate this functionality directly in the .NET Framework.
What are the specific setting and/or scenarios that need better documentation?
Here is a great example of how to create a custom WCF transport channel. Please let us know what further difficulties you have on extending the transport channel.