Quite an edge case, but the accepted encoding types should be filterable nonetheless. I can see a few situations where fine, granular control over this header would be useful (as in adding an API that uses non-standard encoding).
So, while there’s no stock hook for this, I have created a Trac ticket for it and submitted a patch. If you voice support on the ticket, maybe we can raise enough noise to get it incorporated into a future release.