As Nuno points out, you can't have two deployers picking up the same transport package; it is a recipe for disaster.
An option (and maybe the only one) is to have multiple destinations on one publish target, where one destination publishes to the active deployer and one to the passive one. If the active web server fails for some reason, you can switch to the passive one and make that active.
This way, content on both front end environments (active / passive) stay in sync with each other, because if one destination fails a publish action, the whole publish action (so, for both destinations) fails, which is something you'll want. For this scenario, you will need to have two separate deployers (which you need anyway), one for each destination.
Bear in mind that you cannot share resources (like a network share or a broker database) for both deployers. You can of course use a share or the same Broker database with multiple web servers connected to each deployer if you need to have fail-over capability for each logical destination group.