You need to look up sybil attack. What constitutes a node? A port? So all the mining farms do is to split their existing hash rate over whatever you're defining as the limit so they're achieving the same goal.
Proof of Stake solves the sybil by just making it irrelevant on how many nodes your coins are sitting on...
Likewise PoW solves sybil attacks by making it irrelevant from how many nodes your hashrate is coming from.
Also keep in mind that PoS based schemes are arguably more prone to centralization than PoW. Their initial monetary base needs to be centrally issued as otherwise there'd be nothing to stake with, the rich get richer by definition and unlike PoW coins where you usually have a "division of power" into devs, miners and holders with PoS coins all three usually fall into the same, exclusive circle.
That's not inherently true. The coins can be issued with another algorithm, including PoW, where as PoW-problems will not be such an issue, since in an early stage of a coin's existence there won't be ASICs (if it's using a new algorithm) or alone farms for the coin.
It is only true for premine coins, but it should be clear, that premining a PoS coin is a totally retarded thing to do, unless you provide a plan for a proper distribution before you activate PoS.
Blackcoin for instance started with a PoW/PoS hybride that ran for a week and then was designed to switch to 100% PoS. A few thousand nodes participated in the initial mining and before the first bigger pools adapted the coin, the PoW was closed. The developers of Blackcoin never owned a significant amount of coins.
Similar for coins that already exist like Ethereum, these are decentralized enough to run a PoS.
Also with PoS the richer don't get more rich than other. Everyone gets the same interest rate for their balance, no matter if they own 1 coin or 100k, so the distribution of coins remains roughly the same and doesn't cluster up on a few addresses that been rich from the beginning. In PoW the rich, these that can run mining farms, get everything and everyone else gets nothing.
Bitcoin currently has 3 pools that provide almost 55% of the hashrate and Bitmain miners frequently get over 51%. That means the manufactor of the miners could attempt an 51% attack on Bitcoin with a good chance of success.
As said, getblocktemplate-protocol, if implemented thoroughly, lowers the direct danger of pool centralisation but only to some extend. The big pools and mining farms still have a political power in the coin discussion and need to follow coin updates in order to prevent a fork and manufactors of miners could hide a remote control in their firmware to attack the network.
Every wallet has build in a solo mine function. That's unused for years now since pools and ASICs took over and no one bothers to mine on their CPU let alone solo-mine. The initial idea was to run a decentralized peer to peer currency where every participant can at anytime participate to provide support for the infrastructure. That idea is completely broken by now as Bitcoin, Ethereum and other significant PoW coins are almost entirely operated by big mining farms and manufactors in China, who don't have any other interest in the coin but their mere profit. With that motivation, they run the network and influence the coin politics. And that is a bad thing and everything else but a dencentralized peer to peer solution for assets.