Stretching the limits of Notify - notify by category, node type & changing all users' preferences

I'm probably stretch things really too far on this one...and now I'm lost.

I've been following (or trying to follow) a lot of the posts and patches and code additions to Notify to do things the module wasn't designed to do. I've now applied a few patched and added other code in manually that I'm a bit lost and of course finding support is tough. Especially since I'm no coder.

What I'm doing/trying to do/done is, make notify:
1- give options to users to be notified on specific taxonomy categories (I can't recall where I got this from)
2- give options to admins to restrict by node type which node types are included in notifications (i added the code manually from http://drupal.org/node/112657 )
3- be notified of edited content as well as new content (added code from http://drupal.org/node/150109)
4- give admins the ability to apply admin settings to all existing users (useful for existing sites - patch from http://drupal.org/node/36163)

I know this is far from the proper way of doing things with Drupal and since I haven't done it properly, things aren't working right for me (it should teach me a lesson). But I suppose this happens when the author of the module disagrees with the heading proposed changes are taking the module. I am sure it happens all the time and I hope they are not offended.

Anyways...I've attached a .zip copy of what I have active on my site. The changes HAVEN'T blown up my site (which I'm surprised) and it keeps me motivated to come up with a complete solution. But what isn't working now is the changes from #4 above. They are in the .module (lines 66-76) but were added after I did the other three items....before I had the 'set all permissions to the admin settings' working but had to start over in order to add the changes in #2.

AND, I am doubting that the button that is supposed to be created in #4 sets the default settings made from #2 - I doubt it because those two changes are from different authors.

Is there anyone out there that wants to review this 'complete package' (well, almost complete) to see if it can be wrapped all into one? I always think, the more options the better...and leave it to the site admins/users to choose which features to use.