I haven’t tried to pitch something to nginx, but as long as you did it as a clean implementation, “We’re declining to merge, since this is duplicative of code in our paid offering” is the general approach. And then you’re able to maintain your patch set alongside their upstream source.
Assuming the patch is valid, do they decline it citing the paid feature or do something like making a straw man argument against it?