Not sure what the results would be if using magldr with android in nand, but ppl would surely use nand recovery (a few may use sd recovery for whatever reason eg test new recovery before changing to nand and possibly having to increase recovery size). If using nand recovery, then wm6.5 would not be installed, so a check for haret is not needed in nand recovery. Also if using wp7, magldr is sure to be installed.
Also it was stock wm6.5 for eu model, Artemis, other custom and tmous wm versions might be different.
Hope this helps
Edit; Thinking a bit more about this, for nand-only android users, the sd version should surely be the preferred option since you would then have more space in nand for system if there were no recovery partition. No need to increase recovery partition size as and when larger versions arrive, also recovery could then be much larger if needed.
Edit2; Thinking again, to detect haret, you could add a line in twrp2/startup.txt
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=twrp2"
set bootloader "HaRET"
Then test for bootloader="HaRET" in twrp. Magldr doesn't read startup.txt anyway and clk just boots sboot afaik.
I had similar discussion with macs18max here http://forum.xda-developers.com/showpos ... tcount=351 to 357