I think there are just too many variables and too many possible types of patches to make some universal utility to transfer them to M4L devices. You can narrow down M4L device types to Instruments, MIDI Effects, and Audio Effects and determine the types of input/output that must be present for each of those types to function, but a general utility would then have to somehow know how the inner workings of your patch should connect to those inputs/outputs. Then the utility would have to understand which elements of the patch should be included in the device's interface and added to presentation view so it shows up in the device lane. Most importantly some patches, especially those that have timing and sequencing elements, will require modifications that allow them to function in the Live environment. Again, seems like there would be a lot of specific information that the utility would need. You would probably save more time just manually porting your patches. It's not so difficult. Check out one of Gregory Taylor's articles that talks about the process of porting Max patches to M4L.

https://cycling74.com/tutorials/lfo-tutorial-6-live-if-you-want-it/