Nostr is decentralized and there is no mechanism to force compatability. What matters most is compatability between relays and clients that share functionality. If there isn't a shared functionality - go ahead and make lists kind 1 and notes 30023 because its not bugging anyone, just don't expect anyone to work with you on your island.

NIPs repository stands as protocol level standards to ensure interoperability at a base level. This isn't a proposal for a standard at a base level, and so doesn't need to be submitted, let alone asked for permission to be a part of a core set of specs.

Also, me not being a native web developer - what business do I have submitting a proposal for some functionality that is difficult to convey? I'm not wasting core nostr dev's time asking to be merged. If it is useful, implement it. If it is useful but brings incompatability - tell me to change it or fork it. Any worries for interoperability will converge on a shared standard if there is a need for shared functionality between clients, i don't even need to agree with it.