There are several twists that can be adapted to the @wksta.ini or @wksta.kix file scenario. You could still have a central INI or KIX file that defines the attributes for each workstation. You admin script could stage (write individual files for each workstation). This substantially reduces network traffic especially if each workstation will load this file 3-12 times by executing ReadProfileString 3-12 times.
The choice of generating KixTart script '$a="p1","p2","p3"' etc. or an INI file per computer is personal taste. The management of either can be scripted.
There could be some issues with this suggestion, but I think they could be resolved as I learn more of your implementation and desired outcome. One black hole for me is I really have no clue what the change process is. You suggest that coworkers could add printers. But does this mean they used Windows to add a printer to the computer or modified the config file. If they do the previous then you would need a method to capture that fact if the printer addition should be permanent. But who decides that?
