No equivalent of new page patrol for images, let alone Page Curation (using the PageTriage extension, see New Pages Feed on enwiki). Users cannot mark off what Images they have checked, so hard to prevent duplication of work.
Such a patrolling feature should be integrated into the api so that local js-wizards could easily integrate patrolling features into their tools where it makes sense to.
Second step would perhaps be a more integrated tool that allows proposing for deletion, adding {{nsd}}, automatically flagging suspicious pages. Basically the things PageTriage does but for images.
I would propose that step 1 be implemented first, but implemented in such a way that it can be folded into step 2 (So as to avoid having to re-do patrolling system like PageTriage and traditional new page patrol)
In particular I imagine that means not storing patrolling data in RecentChanges table. (Which really is not a good place to store it for a number of reasons). I would suggest perhaps putting in image/oldimage table directly. (Would need to make sure that that can be done efficiently, especially for a "recent images in cat X" feature).
PageTriage involves a lot of cultural assumptions. To some extent that is very difficult to avoid. Thus it would be good to have the two steps integrate with each other, but also be separate so the basic image patrol feature could be used on any wiki, regardless of their cultural traditions.
People come from all over, and sometimes don't speak english. Its hard to evaluate if a file is ok when its description is written in Chinese and you are zh-0.
There is much more bot uploaded content (from glams and things). These probably don't generally need to be patrolled in the same way that user content does.
