There is no way to configure a single EVA so that it can always cover the concurrent failure of two disk drives. With at last 12 disk drives in a disk group, the EVA will start to form 'sub-groups' (=RSSes) in that disk group, which does improve the situation a bit.
Remember that the 'double protection' (level) only defines how much disk space is reserved so that the EVA can rebuild redundancy after a disk drive has failed, but it does not actively protect your data - that is done by a virtual disk's VRAID level.
No amount of disk drives or setting of the 'protection level' can prevent data loss for VRAID-0 when a disk drive has failed.
I have not checked the best practices right now, but I think the recommendation you mention in (1) is just to save some space for user data. In most cases an EVA is under constant monitoring from WEBES/ISEE so a failed disk gets replaced rather quick.
(2): a VRAID-1 vdisk can theoretically survive as long as no mirror-members are lost within the same RSS. An RSS can have between 3 and 5 of such members.
But as you correctly say: it is not something definite...
.