You’ll need to restrict the paths where the Worker is active. In that case it should only run when it is actually required.
One other alternative - if your Worker is actually optional - would be to reconfigure it so that any such requests will skip it and go straight to the origin.
This is exactly what I was looking for.
I’ve set the workers route to FAIL OPEN, and now it will balance the requests to the server once it hits 100k requests.
This is available in the worker in the route settings.