An ideal preference management strategy should allow an admin to set a specified preference value, and if desired, prevent that value from being changed. Due to the nature of Premiere's XML file, only one of those two goals may be achievable. Knowing that, is this still worth pursuing?
Premiere's preferences are located in more than one place and lack proper documentation (from an administrative perspective). Some exploration and observation is required to obtain an understanding of their structure and associated behaviors. Don't worry, things don't get too convoluted.