If your playthrough currently has the AAII science Pack 0 mod (or you aren't playing with AAI Industry), and you have PyCoal Touched by an Angel---from as far as i know: you should be fine.
So part of the issue for me is: Is PyCoal's author going to fix the issues addressed in these two "patch" mods, or will they remain a requirement for people playing PyCoal with these other mods? If he fixes the issues internally, i'll have to address those changes pretty quickly and release a fix within MSP that undoes the work i put in to make them compatible...if not: then i have to hope that all the mods touched by the patched mods-compatibility with Pycoal remain consistant enough to not through any errors with the others.
consider this chain: Any change/update to any of the mods made compatible by "PyCoal touched by Angel" is pushed.
PyCoal touched by angel is now broken. it attempts to change a technology within ... say... bioIndustries, that has been renamed. Users must remove PyCoal TBA, which breaks the fixes it provided to Pyanodon. This results in MSP no longer being able to load with pyanodon because of a strict trinary "lock" that requires Pycal TBA to be there if pycaol processing is enabled.
However: if the author of pycoal processing did proper checks within his code for mods/technology such as if angel's mods is enabled, or such--and ALTERED the way he changed the game to prevent incompatibilities, then the likelihood of the above scenario is decreased drastically.
Also, nothing would really change within MSP if i simply used a "crash game if Pycoal is enabled but either PTBA or AAI science pack 0 aren't there" -- it'd just create a scenario that would not allow the game to load to the main screen.
Also, in my mind, due to the popularity of Angels, bob's, omnimatter---it is likely that either pycoal with address the issues internally at some point, or outright set internal dependencies pointed towards those "patch" mods. Most authors would be wary of pointing a dependency at a mod they aren't the author of, however. So he (or she) may also simply steal, or replicate the effects/code used by those mods to resolve the issues PyCoal+(other) has.
There isn't anything in MSP that explicitly breaks a game with Pycoal. it's actually mostly that pycoal and others aren't compatible between themselves without a third mod resolving it.