Yes, there are specific models containing the configs (HostConfiguration). This usually has a modelName of the device followed by the date/time the config was captured.
If you search for all modelTypes of HostConfiguration (0x820004) and view the attributes, you will see:
0x820073 StartupConfigText
and
0x82002b HostConfigFile
These are the Startup and running config.
Oddly enough you can't work out the contents via vnmsh (at least I haven't found out how to as I think they are encoded). If you use REST and query the value of the attributes you get the ASCII character codes (separated by periods (making up the config). You can just iterate through the string and convert the characters e.g. print chr($int). There are some non-displayable characters like newline and others so you will need to handle this as well.
For configuration of ports, we actually do it the other way around. We require the network teams to add a descriptions and we have scripts which look for this at deploy time and then enable/disable interfaces. It's also easy for other tools like CA PM and eHealth to pick up.
Typical example is to use something like [PRIMARY] and/or [SECONDARY] in the description and then just update the attributes on the port to enable/disable the monitoring.
This way the responsibility lies with the networking team. Alternatively if you have a CMDB and this info is in there you can just use that. (not sure how you decide what ports get monitored).
Also see: