No, I don't want hazel to import into both libraries from one machine.
Consider this network setup: Mac A, Mac B, and FileServer C. Both macs have their own itunes db/library.xml file, but the files are stored in FileServer C in a common directory, exposed via a network share. Mac A adds 1 or more files to its library, and iTunes copies them to their final resting place on C. Now, B doesn't know about this file until I attempt to import it from that machine somehow. Because the file is already in its 'final place', all that needs to happen is for the file to be recorded in B's iTunes DB/xml file.
I want a copy of Hazel to run on both A and B, each monitoring the share on C and keeping their respective iTunes DB in sync.
Based on your description of how Hazel works, this should be possible. I'll give it a try this weekend.