Supposedly, the person who initially submitted the patch to add jpeg xl support has been keeping it up to date in the event that chromium wants to re-introduce it.

If that's the case (and if the implementation is sufficient, rather than a leaky prototype) it would seem that the burden is quite low.