NE adds a lot more than just Outlook support. Hot backups, delegated administration, and cross-server mailbox moves are important even if you're just using imap. You're potentially looking at a lot of sysadmin time to make multiple editions work together, and you're adding risk. What if the talented person who cobbled together the custom solution leaves the company?
I ran OSS-only mail for thousands of users for ten years. I wasn't thrilled to start paying license fees for the first time, but I have found support to be well worth the cost. Perhaps it helps that .edu pricing is lower, but still, if email is business critical, you and your management have to decide where the tradeoff is.
That said, you could make this work by setting up a "split domain" configuration; see discussion in the user migration wiki. In theory, you could even make the global address list comprehensive by defining one as an external LDAP client of the other and using zimbraGalMode=both. You would have to study the NE license agreement very carefully and check with sales to make sure this is legal.
From a purely technical perspective, I would probably advise *not* running a split domain. You would save yourself some complexity, hence risk, by making one system a subdomain. For example, configure OSS as example.com and NE as corp.example.com. If necessary, create forwards on the OSS box for
the_boss@example.com =>
the_boss@corp.example.com, but enforcing the rule "some corp users can only talk to other corp users" might be easier if you don't set those forwards. Or you might end up putting those restricted users in a third internal.example.com domain defined on the same server as corp.