You are not explaining your architecture. The parent (and me as it happens) assume that when you paste the URL and change params then that URL is sent from your browser to a server. The server runs the simulatíon based on the params in the URL it received and returns the results to the browser. With that architecture you would need a lot of resources for the server but not for the browser. What architecture are you thinking of?
Server is just a dumb nginx server sending HTML and Javascript. No dynamic routes. Everything happens clientside (main thread and/or web workers, local storage for persistence).
