If you're OK with having a second URL for the document-literal style web service you could just extend your existing CFC. Your new CFC would have all the same functions and logic of the main web service. It would also prevent a There would be no additional code to maintain. The only unknown for me is if this will create any significant additional overhead.
<cfcomponent extends="yourExistingCFC" style="document" output="false"></cfcomponent>
I did try setting the document type to document-literal on one of my test web services. SoapUI was unable to parse the document-literal WSDL once changed, but Visual Studio could. From this, I would be hesitant on changing the document style of your existing CFC, for you cann't tell how all the client environments will handle the change.