I'd be happy to stand corrected but I don't know of any way to do that with swiping.
Instead I would use animations in an MSO which each state triggered on state load. The fly in or fly out effect would probably be sufficient to get you close to what you want.
I found a way to create a "fake swipe" that might work. I'll have to try it out one some other people. I left the MSO as it was, but added two transparent buttons on top of the image stack--one on the left half and one on the right. The one on the right goes to next state. The one on the left goes to previous state. If other people are like me, when they want to swipe forward, they touch the right side of the screen first, then drag R->L. To go backward, I touch the left side of the screen first and drag L->R. So it's still operating on the tap, with the drag being irrelevant, but it does mimic a swipe.
I doubt that’s going to work. I would test it out with a small focus group before I went in that direction.
IMO, you’d be far better off with a visible next and previous button that make things obvious. There is zero reason I can think of to try and force this into the document and make things harder for your readers.
Hiding things like this makes for a very poor user experience.
I ended up going with both. I have arrows, but I also have a swipe. So there are two ways to go backward and forward.