Populating Address Space using the UANodeSet is a bootstrap operation and adding full-featured code to the codebase could be recognized as wasting resources. This code should provide a validation procedure that yields a few hard questions. An alternative is to populate Address Space using a custom format requiring minimal resources and delegating the validation and translation functionality to external tools (like asp) that may be used at the design time before deploying the server in a production environment.
My point is that export functionality to UANodeSet is required only and only in case the Address Space (AS - source of the model) is embedded in a design tool - it is not required that it is an OPC UA Server. To save the current state of a full-featured server the AS content can be written to any custom file format without breaking any compliance rules.
Hope it helps. Let me know how it works for you.