I've had this problem with both Debian and Ubuntu. Sometimes the patches they apply are good, sometimes bad; but I wish they at least had a social norm of "contact the upstream project and offer them the patches". It's annoying when the first I hear about a patch is when a user contacts me to complain that something is broken.
I understand if you feel like your responses are being ignored. I was focused on other things the past weeks, I'd love to be more responsive.
WRT patching things in weird ways and not contributing back, I don't understand it.
We are shipping three patches in Ubuntu:
(1) Changing from Arch's /etc/conf.d to the Debian/Ubuntu /etc/default directory.
(2) Switch form /etc/networkd-dispatcher to /usr/lib/networkd-dispatcher.
(3) Running with --run-startup-triggers by default.
(1) and (3) are distro-specific things. Sure (1) could be made an option somewhere or something, but that sounds more complicated than just fixing the path to match the policy.
For (2), I opened a bug about supporting both directories. The most important part for us was having the ability to package our hooks in /usr for the 18.04 release, though, so I had to quickly patch that in. I fully intend to support both paths and then send you a pull request, but I think it's clear that a pull request at the current time would not be worthwhile.
I hope that this addresses your concerns.
This does not seem like 1) a good model for floss developers to give a shit about Canonical, 2) a good model for Canonical to support (non-corporate?) users