Jiri,
I have to disagree this requirement is not popular.
We also would like to see NCM be able to have visibility into the interface configuration. We have the need to detect whether a "bandwidth" statement is configured on WAN/uplink interfaces to be able to apply the appropriate QoS commands to the interface. We are trying to migrate away from Cisco's QoS Policy Manager (QPM) product and if NCM had this feature we would be able decom QPM in a heartbeat and in a matter of days. With NCM only having visibility into the interface description we have resort to having our engineers start inserting a keyword into all the WAN interfaces description that we can have NCM command script detect and apply the right QoS statements. This manual method is unreliable whereas keying off of a required interface command eliminates ensures no interfaces are missed when executing the NCM script.
Another use case would be able to determine whether an interface is a trunk or access port to be able apply switch port security commands. In addition, knowing whether the port is trunk or access, to be able to apply configurations like netflow, ingress/egress ACLs, OSPF cost, and ip helper (as in Steve's case) commands to an interface.
Edit: And, I almost forgot, be able to apply/remove configuration commands based on whether interface is "shutdown" or not.
NCM having this increased functionality would really make NCM command scripts more robust and powerful.