Server and client handles physics logic without replication

My game is very physics intensive. It is a good Idea to parent the model affected by physics in Workspace.Camera for the server, so that way it doesn’t replicate to client. The client also have a copy of that model. Both the server and client handle logic independently. With the server have an extra task to send data to the client using attributes signal, the client can receive that signal and handle physics such as unanchor parts or create explosions accordingly. Late joiners can also request the data from the server to load the current destructible map. My goal is to increase performance this way. Are there any other options. Also my game uses welds so that collapsing a building looks more cool.