I know where you're coming from here. All I can say is there is something else wrong in this case and this is how it's being expressed. I've seen it several times myself and sometimes no amount of good coding can fix bad architecture.

But I will say that if the twenty use cases all grow to the point of needing their own abstraction, I think you'd be damn glad there was at least a point of separation instead of having to maintain all possible permutations in a single method signature.