Negative ramifications of "ConformsTo = WsiProfiles.None" in C# web services

Question

I'm adding a method overload to an asmx web service written in C#, and in order to publish it I need to change the WebServiceBinding attribute of the service to the above. Doing so seems pretty harmless (the web service will only be consumed by applications written in house, at least in the foreseeable future), but am I missing some implications of that choice?

Answer 1

To implement method overloading in webservices first you must set the MessageName
attribute of your webservice then set your webservice binding ConformsTo 
attribute to WsiProfiles.None and that’s it! Note that you can do second step 
in your Web.Config file for all webservices.

(according to this blog post).

Answer 2

Just to wrap things up here (after @Niklas's query), I decided that worrying too much about this on an internal-only web service amounted to micro-optimization.

Specifically, I determined that as long as no one is going to generate a proxy from my WSDL for the service and as long as all of the consumers are well-known (and in this case under my control), the WS-I profile I conform to is irrelevant.