When making suggestions, try to differentiate between what is intersubjectively or objectively bad or wrong, and what you simply dislike on a personal level.I don't think subjective opinions are necessarily bad, and disliking something personally can still have merit - since I think most people agree that getting maps to the point where they're played because they're fun/challenging, and not unfair/otherwise is the end goal. I feel like this bullet point is a little bit better addressed in the main parts of the suggestion list you have. Imo it essentially boils down to, consider your mod to be a dialogue to the other mapper. If it's simply "move x to y" the whole time, or "you missed a note here", there might not be much need for elaboration, but when explaining patterns and expressing dislike, whether subjective or objective, it should be on the modder's side of the field to make sure the mapper understands their point of view.
Start with small changes to preserve the existing concept of the beatmap. Try more significant changes only if necessary.I think this is much less a code of conduct thing, but a general modding guideline? Not sure how necessary this is.
Like, if this is a code of conduct, a lot of that section I feel like can be condensed with the "responding to a mod" section, because in the end, it's everyone wanting their maps to be better assuming the code of conduct is followed, and a "treat others the way you want to be treated" kinda comes into play i think.
========================
I'm actually the most confused about giving kudosu. Mostly to BN checks, and repeated mods, what's the policy on that - I've never really seen any real set in stone thing other than "give kudosu to mods you found helpful, even if you didn't apply any changes to your map"
Also, with modding v2, potential changes to the kudosu system or something may be happening as well?
========================
good guidelines though, based off of literally "common sense. think about what others are thinking. don't be a diq"