When is Modbus.ini loaded and can you force to reload after?

Question

To effectively complete the Modbus disable task with the modbus.ini file entry "SkipImmediatePoll=1" and a high poll-rate time and/or a poll value of false, I need to know when the modbus.ini settings are loaded, and whether I need to restart any process with modbus objects, modify any running modbus object, restart lookout....etc. Also, can I force a reload programmatically? (suggestions welcome)
Ed

Answer 1

Review/Clarification for all those interested.
I need a way to turn modbus device communication on and off within a running process, to avoid wasteful computer resources timing out on communication with disabled Modbus client devices.
So we can enable "skipimmediatePoll" for [Modbus_X] in the Modbus.ini file and then set a very long poll-rate on tag Modbus_X. This, so far is the best way to minimize the lag at process startup so that working devices get polled much sooner.
Why I ask if the Modbus.ini file is parsed whenever a Modbus object is modified, is to provide an easy method to turn the devices effectively on/off by just changing the poll-rate back to normal after editing the Modbus.ini file, all while the process remains running.
Of course it would be
nice if I could force the Lookout.ini reload without restarting processes, then I could reload the .ini file and dynamically change the poll-rate while the process remains running, effectively switching the client communications on/off when necessary. Even better, I could programmatically edit the .ini file, reload it (somehow) and modify the poll-rate, all within a running process.
Basically, I need a way to reload modbus.ini settings without reloading a process. Alternatively, I could just load/unload a dummy process programmaticaly. I just need to verify the behavior of the modbus.ini file settings and existing/new modbus objects created/modified, knowing exactly when the settings get loaded for sure. For example, say I load a dummy process with no modbus objects in it. Will the .ini still reload? Will it affect modbus objects in already running processes whether the dummy process has or has no modbus objects within it?
Thanks All for your interest and particip
ation.
Ed