This is exact the way of thinking I would like to have changed!
Whisper and Swarm are not only that debatable cases. I doubt even ABI standard “is required to make an interoperable main net client.” because there is no ABI on the EVM level.
Main-net connectivity and consensus relevance should not be ONLY the criteria to decide what is Ethereum and what is not. Any list of relevant Ethereum technologies is welcome, but EIP process in its actual version is wrong place for that. Current EIP process is too focused on Core Client development, led by Core Dev Editors, while huge value of Ethereum depends on ecosystem outside the Core.
We should extend and decentralize EIP process first before we try to press the whole ethereum universe into it.
More reasoning I have made here (sorry for shameless self-reference).
Once more, I would support any approach for “Highlighting the other standards & specs that make up Ethereum” but not as part of current EIP process - it is not suitable for this global task. It will be either ignored or will hit development dramatically.