The short answer is no.
Each masternode requires its own wallet with the darknet.conf matching the example, using a different private key. So, to have 2 masternodes set up following this example you would need 3 wallets, 1 for each masternode, and the wallet that holds the coins for each masternode and acts as the controlling wallet.
The "1" in the masternode=1 means true, "0" would mean false, "2" would not be applicable.
I don't understand why we need a separate wallet for each masternode. I followed this guide here.
https://dashtalk.org/threads/reubens-start-multiple-masternodes-from-one-wallet-guide-start-many.4034/It's from the masternode guides sticky at the very same forum. If the guide was bunk, I find it odd that it would be in a sticky on the official dash forum. At the same time, I was under the impression that you needed different ports and/or external IPs for each masternode so I don't see how that is possible if all your masternodes are running off the same wallet.
This guide kinda sorta works for a while. I get payouts but not as frequently as I should and there are lots of masternodes going offline with "expired" or "missing" messages. I just figured that if there was anyone I could trust about masternodes, it would be DASH fanboys at their official forum but apparently not.
That guide is only partially complete, it makes no reference to setting up the actual masternodes, only the controlling wallet used to start them. If you notice towards the beginning the environments used for the guide were mentioned, Local: Windows 8.1 64 bit, and Remote: Ubuntu 14.04 64 bit. In all likelihood the remote was on a VPS, as that is the most commonly used practice in any of the Dash masternode tutorials.
That guide assumed you had already set up masternodes elsewhere and were looking to control all of them from one wallet. If you don't have a wallet running as a masternode, and only put the information in the masternode.conf when the network looks for available masternodes it will not see your masternode, as the wallet doesn't announce itself as a masternode without masternode=1 in the darknet.conf.
A wallet will only function as a masternode for 1 private key, that is why each masternode needs its own wallet.
The reason your masternodes are expiring is because they are not actually running. You tell the network when you run "masternode start-many" "hey, I have some masternodes running at these addresses", the network takes your word for it and adds them to the list of available masternodes. The network never actually sees them, and they go to expired when the network doesn't see them for an hour or so.
I hope that was understandable, I am not always the best at explaining things.