I am currently installing a Umbraco website on a load-balanced environment which was already in use for another application.

This load-balanced environment is configurered so that the webservers are replicated by copying the master-webserver. 
For this environment we have installed the CMS on a single seperate server which is not part of the load-balanced environment and we are publishing content to the Master-webserver.
This is done by setting the Distributed Calls to true and configuring the CMS server and the MASTER-webserver.
(small note, the slave webserver cannot be entered here unfortunatly)

Now we are experiencing the issue that, after publishing new content, the MASTER webserver receives the trigger to reload the content and updates the Umbraco.Config. The new content can now be seen on the MASTER-webserver. BUT: When the replication is finished, all the Umbraco.Configs on the SLAVE-servers is renewed on disk, but not reloaded in memory. 

Is there any way on making the SLAVE Umbraco installations reload this Umbraco.Config when noticing a change on disk?

Hope anyone has a idea :)