Now, obviously you can't prevent the actual data from being distributed. For example, you could base64 encode the image and send it as a series of messages instead.
The motivation for revenge porn is to hurt the other person. One vector for this is to post it to all of your mutual friends so that the victim is shamed. This adds a barrier so that the mutual friends have to invest work into getting and distributing the porn, and won't accidentally see it flowing through their feed.
Technology for searching for similar images (I have no idea how it works interally) already exists and is very widely deployed. You can easily find an image similar (uncropped, cropped, with different filter, greyed, ungreyed, with a logo in corner, etc.) to your input image on https://tineye.com/ and https://images.google.com .
If you had access to the original implementation, you could probably defeat them permanently with minimal alteration via reverse engineering. Which is why you don't have access to the original software, its specifications, or implementation details.