It would be a very rare thing for such a conflict to arise. And you would have to go to quite some trouble to create a conflict that could not be resolved trivially. Is there something in particular about your module that's making you wary in this regard ?
Unless your module overwrites the files that PPM uses internally (all of which reside in your perl installation), I can't see that any such concern is warranted - especially if the module is not going to be installed via PPM, and if there's not even a PPM package for it.