Let me first re-direct you to the Lisk Delegate Handbook:
https://lisk.io/documentation?i=lisk-handbooks/DelegateHandbookThere are some discrepancies in your understanding of how voting works, I would advise to read the recently drafted Delegate Handbook for a detailed explanation.
Now, to explain it as best as I can in my own words.
Your account has a voting presence that equals the amount of funds you have in your wallet. The more funds you have in your wallet, the higher voting presence it has. This account can vote for 101 different delegates, you cannot stack voting. Here's an example:
John's account has 15M LISK, he has a voting presence of 15% (out of the possible voting presence total of 100%)
James account has 10M LISK, he has a voting presence of 10% (out of the possible voting presence total of 100%)
If John and James were to vote on delegates, they would account a total of 25% vote presence on the chosen delegates. Keep in mind again that they may not vote twice on the same account, they must either a) not vote b) vote on the desired accounts only.
A simpler way to view this is, if one person holds all of the funds (100M), he has 100% voting presence, and has complete dictatorship over who will be the 101 active delegates. However, as stated previously, you don't need 100%, 51% is enough to rule the other half of voters.
This brief explanation may not be the best, so I would advise you to read the Delegate Handbook thoroughly. Your concerns should be answered.
In order to determine the delegate rank position, Lisk has a decentralized voting mechanism built directly into the client. Users can vote for any delegates registered on the network. One vote equals 0.00000001 LISK, and a user can only vote with his entire LISK balance. One vote costs the user 1 LISK and he can vote for 33 delegates in one go. He can vote for 101 delegates in total, for this he needs to initiate 4 votes (33+33+33+2 = 101). It is not possible to vote for the same delegate twice.
The number of votes are represented as an Approval within the client, and is shown as a percentage. An approval of 1% equals 1% of all LISK in the network. At launch this would be 1,000,000 LISK (later more, due to inflation) or 100,000,000,000,000 votes.
I'll accept that this is a reasonable system if a balance vote is split among the 101 delegates. For example if a wallet has 101 LISK and votes for 101 delegates, each would get 1 LISK worth of vote.
However,
the way the above reads is that if a wallet has 101 LISK and votes for 101 delegates, they each get 101 LISK worth of votes. If this latter case is true, then the whole network could be controlled by someone who simply holds a plurality of LISK.