Not sure if you already found an answer to this. Even we had a similar requirement wherein the service provider had shared us a WSDL and later removed some not required @WebMethods
from the Web service implementation file.
However, on invocation of the other methods there was an error as below which led to the conclusion that the WSDL file is validated during the web service call.
javax.xml.ws.WebServiceException: Method XXXXX is exposed as WebMethod, but there is no corresponding wsdl operation with name XXXX in the wsdl:portType
We changed the approach to read the WSDL file locally by having an entry in jax-ws-catalog.xml but even then on dynamically binding the end point the WSDL at remote server was validated and gave the same error.
And yes adding a new method does not cause a harm from the client invocation.
Hope the answer helps.