Hi Thilo,
I haven’t looked into this from a protocol perspective yet, but from a server developer’s point of view: even if we implemented this tomorrow and released it in a few months (which is pretty fast in server time), keep in mind that many server admins update… let’s say… at their own pace.
That means new features often reach only a subset of users at first. This is not as dramatic as it may sound, as it happens for all new server features. Usually, it is fine: early adopters naturally gravitate toward servers that keep up to date anyway. But if your solution requires broad deployment to really be useful (which might be implied by the fact that you're explicitly asking for server developer perspectives) it might be worth considering alternative approaches.
Kind regards,
Guus