I've been taking my time with this and getting the zones right. Last night I decided it was stable enough to start adding FP2 zones into automations. Using HADB, I have brought the zones into HE and they appear as highly responsive motion sensors. Perfect! 
Once they are in, I'm using the Home Assistant HomeKit Controller integration's sensor view to know when a zone is activated or not. Probably works the same with the Apple Home app, but I'm not using that, so I cannot comment. This is far better than trying to use the detected person icon on the Aqara FP2 Zone map. It would be great if the app worked perfectly, but it often doesn't show you as present, even though you are detected (which I'm determining by looking at the HomeKit Controller sensor view as previously mentioned). This allows quick and accurate adjustment of the FP2 zones. I simply open the Aqara app and make a Zone adjustment, save it and then flip to Chrome on my iPhone to see exactly when I'm detected in Home Assistant or not as I move in and out of the zones.
It's early, but I suspect that what some people are seeing as ghosts in the Aqara Zone map, are merely in the Aqara app alone. A bug in the app, and not a problem with the actual FP2 1.15 firmware I'm running. I'm finding no actual person detected in that zone when the app shows that a ghost exists in that zone. Again, I may be incorrect here, but the evidence I'm finding of actual detection when viewing the HomeKit Controller sensor status indicates otherwise. However, if you have upgraded to 1.17, this may not be the case. I'm sorry if you're plagued with poor performance due bugs in 1.17, and I empathize with you. As I mentioned in my previous post, circumstances both within, and beyond my control gave me a second chance to avoid the allegedly faulty 1.17 firmware the second time around, and I can now safely wait for the next release and see how it shakes out before making the non-revertable choice to upgrade.
Hope this information is helpful and I'm interested to hear if anyone with FP2 firmware version 1.17 can either corroborate, or confute my findings using the same methodology. 
