Oh I love it when people say this.
Explain who is being taxed?
Answer NOONE The network itself out of its funds is paying it as a reward (payment).
Very much different to being taxed. Just like a professional charges for services provided so too the network itself will pay the professionals who do maintenance on the network.
As to many of your other points, a little deeper looking into things will solve your queries. For instance it is usual as in the internet usual, that is like a web-server or nntp-server and is not referring to older network definition of server on a peer-to-peer file serving local network where each computer has certain files held. Its trying to point out that there is no single point of call to do the transaction, it is distributed with one bit of data handled by one section and another by another section and independently of each other. In other words not the usual usage of the term server. And also as David said
When you get to understand the nature of consensus then you realise that you need to take over a section in order to change the protocols followed including how rewards are done.
I cannot see it till Friday morning, so don’t feel bad 
Only if you want to do this. Its just one feature available to people. It has its usage and really quite obvious that privacy/anonymity between the two parties is not there. But SAFE allows them to set it up without intermediaries.
If you don’t want this specialised situation then don’t do it.
I like that you stick to your guns. But the facts don’t support it. What facts you say, well the testnets when we had vaults at home and the network worked great with vaults (thats right redefined word) servers on home computers. If the vaults handled (any) transactions sent by a user then yes it would be called a server in the usual internet usage of the word. But the safenetwork is such that the vault only stores a small portion of the whole data and only participates in a very small number of the total communications in the network. There is no “load balancer” or we’ll store Joe’s data in this vault and Mary’s data in that vault and Joe’s transactions are handled by a specific vault etc. Its a distributed network and vaults work in a P2P configuration rather than a client-server configuration. Your definition really does have any device that supplies a packet is a server.
If you read what David was saying again, there isn’t technically a queue, but rather if you offer up your computer as a Node (vault) then it is assigned a section to (attempt to) join. If that section does not want a node then your attempt is rejected, not queued. You have to try again to join the network which means you will be assigned to another section to try and join it. No queueing
You keep saying this and that doesn’t make it true.
There maybe some advantages but there are disadvantages to running a server as a vault. (compared to a suitable home vault)