It has also just occurred to me that there exists instances of multiple simultaneous types of FCS systems being employed for a single weapon/unit, for this reason the Task is edited as follows:

For clarity, I'll be using example cases (numbers are not exact, but demonstrative) for such scenarios for both the unitAimPosition command and this one; the ones where they'd provide an identical result, or one that can extrapolate an identical result are in bold underline.

What an object/AI knows about doesn't always equal what the sensor currrently sees.
Also sensor view range can be adjusted by player, I guess this script command would just either ignore sensor range, or use max range

Just for clarity of the request and what each value means, whether or not 'threatlocked' is added is up to you.