Not to argue with any of the above advice, all of which is good.
But I have to share some observations or insights or dumb ideas (take your pick) about 4e rules interpretations....
There are a lot of items and powers that are in essence 'exceptions' (per 'exception based design') not so much in that they clearly spell out an exception, but in that the way they're written, they don't work unless you cut them a little slack when it comes to when an immediate action, especially a reaction, can be triggered and by what. That's one of the trade-offs of the 4e design philosophy vs the hard-line RAW of 3.x or the rulings-not-rules of 5e. How an individual instance of a rule works can contain an exception, so it can be clear how that instance works, but when a general rule is tricky to interpret, you can't look at clearer/more-specific instances for guidance, because they're /exceptions/.
Ready is a more general rule, so it doesn't get cut any of that slack. You need to ready in response to something. Readying an attack when an enemy moves within reach, for instance - you can generally see him move, no problem, he gets close enough, you hit him. Even fairly simple ready tricks like that can mess with some things, though. For instance, if a monster has a very powerful immediate action power, readying to attack it on it's own turn in whatever way seems expedient can prevent that power from being used. Overruling how ready works in such cases is one way to go, changing the power to a 1/round free action or non-action though can head it off in the first place. The former would be the '5e way' - just rule however works at the moment, RAW/RaI/prior-rulings notwithstanding. The latter is the 4e way - fix the rule up front, and fix the 'right' rule, the specific one, with an exception to the normal rule, don't change general rules to make specific cases work better.
Based on that, Readying for 'targeting' is something I'd hesitate to allow. It's little more than intent, I'd expect readying vs an attack, and it'd be a reaction to the attack, not a hair-splitting exception that 'reacts' to the attack roll or the hit or miss before the damage roll. Those are necessary for a lot of weird little powers, leader abilities, magic items, and the like, but they're not precedents for 'Ready.' There are no precedents in exception-based design. By the same token, if the only concern is that this ready-to-attack-before-an-attack trick is going to break a specific power or two, you could also just address the potentially broken power...