Think about this for a second. You have a live tracer that depends for its existence on the frames that went before. If you don't render those, then that data doesn't exist (to the renderer), which explains why the tracer can't just miraculously appear correctly for any 1 frame you choose to render. To make that possible you would have to render the entire animation to individual image sequence, or bake (cache) the animation.
Baking is best done to Alembic by selecting the tracer only, r-clicking it in the OM, and using the Bake Alembic option. You can also use Bake Alembic and delete to remove your original tracer at the same time, but you should probably keep that in case you need to go back to it and alter settings. However, if you do let it remain, you will have to take it out of the sweep or it will act as a rail for the baked tracer, and break it. But now you can render any frame or range of frames, and all should work.
For your general information, there is also some incorrect ordering in the Object Manager, which may not be the direct cause of the issue, but certainly doesn't help. You may not be aware that Cinema scans the OM downwards from the top. So first it encounters a sweep containing a tracer that refers to a matrix the scene doesn't know about because it hasn't reached it in the OM scan yet. So the Matrix should always be BEFORE (or rather I should say ABOVE) the tracer in the hierarchy.
CBR