Note (August 2008): Thanks to all of the users who have provided feedback on these proposals. At this time, NI is likely to proceed with the proposed LabVIEW API to access system directories. However, NI has suspended plans to implement the proposed changes to the LabVIEW directory structure. The proposed LabVIEW directory changes originated internally based on anticipated demand for NI to adhere to Microsoft Vista's directory recommendations. Since imposing a new directory structure impacts Alliance members and many of our other customers, we have decided to suspend these changes until there is a greater customer demand.
Hear, Hear! I second your goal to document how 3rd parties can integrate addons and plugins into LabVIEW.
...Facilitating environment customization and replication....I guess this would also include improved upgrade process. Did you see the earlier post to this forum titled Improving the LabVIEW upgrade process? After reading your post, you will likely benefit from having a directory structure that separates out application files from shared files from user files. Right now your personal addons and plugins are mixed in with NI files and other 3rd party files. Furthermore, if you share a machine with someone else, your files are mixed in with their files. If all your personal files and customizations were localized to your User space, identifying what to share between computers would be easier.
Whew...this is a rather long post. I should call it quits...