Method has overload with CancellationToken support

Couple of questions about this refactoring...

When I apply the refactoring it uses the named parameter even when adding the CancellationToken would be unambiguous e.g.

    qualification = await AdminClient.FindCreateUpdate(qualification).ConfigureAwait(false);

goes to

    qualification = await AdminClient.FindCreateUpdate(qualification, cancellationToken: cancellationToken).ConfigureAwait(false);

I then get an immediate "Remove redundant argument name" suggestion - can't it check before it applies the change?

Secondly, is there any easy way of applying this sort of refactoring namespace/project wide