As far as I remember our discussion, remapping should actually alter the image. This could be implemented easily in a single ImageProcessor that consumes an IImageSwizzle-like interface as a parameter.

This also seems a pretty good candidate to use the value delegate trick (for those unfamiliar, I mean using a struct type implementing an interface and making the method generic with the T : struct, ISomeInterface constraint, instead of taking an actual delegate like a Func<...>), since if I'm reading that linked OpenCV correctly, you'd basically have to invoke two custom functions to map the x, y coordinates of every single pixel in the original image 🤔
If there were two non-inlineable callvirt for each pixel, that'd be quite the performance hit.

@Sergio0694 Of course having 2 delegates calling for each coordinate x and y could hit performance in the situation you described. That's why I also included a sample from Kanvas, where a Point struct is just taken in, modified, and then returned. That might at least reduce the delegate count to one. But however you want to implement it, is of course the decision of this team here. I just gave my input on already existing examples for this kind of operation.