After at least 50 tries of different combinations that failed, I resolved to start with what I knew. I knew 2 of the 5 had ILS that worked. I looked at the 2 that did work (with ADE X v1.50.11) and noticed that the FSDT afcads actually had ILS entries.
Of course they work, as you said, the FSDT AFCAD have entries for them, and they worked, there aren't any other ILS at PHNL, the real life airport only has normal ILS on 2 runways:
8L and t4R
Then, there's the LDA offset localizer for 26L, which will show only as a localizer, and might not be tunable outside its covered arc, so you might have to approach from the south-east to tune it.
There are no other ILSs at PHNL, all the other runways have non-precision RNAV-GPS approaches only.
So far it's worked like a charm.
I'm not sure what other ILS you were expecting to see at PHNL however, it's still very likely you DID had a conflicting AFCAD, it's easy to be misled without knowing how ADE works:
FSDT PHNL has NO ILS entries! We haven't added any, and the original XML source code for it doesn't have them, if you really want to be sure of this, simply decompile it using the BGL2XML decompiler, which is a companion utility for ADE (a separate download, though)
You were misled into thinking there were ILS entires in the FSDT AFCAD, because when you load an AFCAD, ADE will ALSO display Navaids coming from the default scenery, because this is what would happen in FSX when you load an airport, the default navaids would still work, unless you redefine them in the addon airport.
Since the ILS didn't need modifications comparing to default, we haven't included them, there's no point including an identical copy of the default data in the scenery, usually ILS are added only when their frequency changes, or when the runway position in the addon airport doesn't match the default one.
In fact, if you *move* or *edit* an ILS in ADE and save it back the modified AFCAD, it WILL include the modified ILS in your saved file. If you don't touch navaids, the file will be saved back without any navaids, as it were UNLESS you select the option to "Load Stock Data" which copies ALL the default data for the airport INTO the AFCAD you are editing.
That's why is still possible you had AFCAD issues because, if the ILS that didn't worked (provided it's established that only 2 ILS and 1 LDA are present at PHNL in real life) now work after loading stock data, it means there WAS another ILS in conflict OR your default scenery was modified somehow because, under normal conditions, PHNL (and all the other airports too) should work without adding any ILS to its own AFCAD, because the default ones will be active.