> Edits can be seen as just another note. So the performance argument does not apply anymore than saying a sudden increase im users would kill the network. 

This is not true either.

The client needs to actually fetch the edit before displaying it. Currently to display a note you only need to fetch that note and you can cancel the request immediately after receiving the response from one relay.
If you are waiting for edits, you need to wait until all relays have answered (within some timeout), to make sure that you are receiving the most recent edit.

Maybe the performance cost of this isn't very significant at the relay level, but it may be more significant at the client level.

> Relays will do what thay can what they must, which includes everything from charging to curating. And users do what they must, from paying to running their own relay.

Personally I'm in favor of relays neither charging nor curating (beyond having some way to remove spam and illegal content) and users to use them interchangeably without thinking about it. For this to work, we'll need relays run by nonprofit organizations.