You can always pass environment variable with property or tag and use it as a rule for management zone. In such way simple rule will be static, configuration will be done on host level.
I rather suggest custom property, to keep environment clean but it always depends of your needs.
Thanks for your suggestion Sebastian, that's not going to work for me. I need to segregate at a lower level than host. If I have 20 instances of application X running on Host 1 I need to be able to attribute each of those application instances to a different environment instance. They all run on different unix users and I am able to map unix account to environment elsewhere so I'd like to make the same distinction in DT.