There you go-

I wasted half an hour deleting objects and trying to purge orphaned data, only to make a three times larger blend file which killed Blender 2.8 really fast just trying to load it!
So here's the actual file, tried it again in 2.8, only the armature parented to the path is moving, still works fine in 2.79b.
Just rewind and press play...

Here you go-

I think I must have tried it in Blender 2.8 and saved it inadvertently yesterday (still loads in 2.8)- if I load the old scene into 2.79 it croaks quicker than Usain Bolt signing up to do a Virgin advert, so I had to rebuild it.
Render frame 52, then try frame 53 (I'd make a coffee while it's cooking unless you have some seriously fast GPUs in your machine!).
Using 'start on frame' for the motion blur give the bullet-time streak and the see-through character on frame 53 as well (same as 'center on frame'), while 'end on frame' moves the effect to frame 54.
I'd drop the tile size down to 256 or so for the bullet-time frames as well; first time I tried it killed CUDA and I had to save & restart Blender before it would render it again.
It's a similar story trying this scene in 2.8 as well so the fault/feature seems to persist there too.