This makes sense. When using the shaking reduction, you’re intentionally asking to reduce the amount of motion prediction. But when using motion reprojection, you’re effectively increasing the amount of latency for (re)using the rendered frame. Reduced prediction + increased latency = larger prediction error, leading to overcorrection, hence wobble.