First of all there is no 'image REST resource', so the short answer is no.
However you can save images as complex obs of course. But I can say, for having played a bit with this for VDUI, that the current implementation of the obs resource doesn't quite handle the case of complex obs. For instance we had to create a custom
ObsResource to properly handle deletion and certain types of edits. See here.
By the way this example shows that you don't really have to worry about (not the core but) the REST Web Services module, you can just add resources or extend existing resources through your own module(s) anyway.
In the context of VDUI I scratched my head a lot over this one: should I really be text book REST-compliant for the upload/download of the data behind the complex obs?
This would mean Base64-encoding/decoding all the time. At first I thought that there would be a performance issue, and there is one but I don't think it is really meaningful. However for VDUI this option was not really working anyway since not every content can just be Base64-encoded, especially when you don't know in advance which MIME types you will have to handle. And that's the use case for VDUI: it implements the handling of certain MIME types in a specific way but otherwise it deals with the content in a generic manner.
But if you know that you will always deal with images, then you can certainly create - say - an
ImageObsResource and ensure that
DELETE... etc are implemented according to your needs.