Hello there Engima, and welcome to the wonderful world of Arma Editing!
You're quite correct as to how knowsAbout works, but I don't really see the problem? Let's say unit1 knowsabout the player, and sends unit2 to the player's location: as long as these two events are simultaneous (unit1 spots player, collects player's position, and then orders unit2 to move there), there's nothing stopping the player from moving on from that position and out of unit2's way. To wit:
waitUntil {unit1 knowsabout Player > 2};
_pos = position Player;
unit2 doMove _pos;
unit2 will now simply move to the "last known" location of Player, rather than the player's current location. You could in fact do away with the _pos altogether, but I added it to make it clearer how the engine handles this: "position Player" is simply an array of numbers, and once that array of numbers has been given to a unit via doMove, it's not going to change unless you issue a new doMove (e.g. in game, if you give the order "move to that car", and then you drive away with the car, the AI will not start following the car around, but go to where the car was at the time the order was given).
However, there is also one other, more modern command you could use instead of knowsabout:
nearTargets. This will give a list of all known targets around a unit, including a -perceived- location, which is actually even better than the above. This is the location the AI -thinks- the enemy is at. You've probably experienced this when for instance your squad leader gives you an order to engage an enemy, but the red little square isn't actually pointing at any enemies: it's pointing at where the SL -thinks- the enemy is.
Using this command is considerably harder though, so the question is: what are you trying to do, and will the above solution be enough?
Wolfrug out.