Hi there,
I think verion's approach is the best way to fix this if you want the fastest image loading in attractmode.
As a bit of background to what is going on: When attractmode tries to load an image it first uses SFML's built in image loading routines. If that fails, it falls back to loading the image with ffmpeg (which isn't really meant for image loading but does the trick).
So I suspect what is happening is that SFML's image loading routine thinks the images are corrupt and spits out the error message you are seeing, but then attractmode falls back to ffmpeg which is still able to load the image (in some cases). The slow down is from attractmode trying twice to load the image, with the ffmpeg call being the slower call.
Attractmode never tries to write to image files (except for screen capture), so it shouldn't be the source of the corruption.