There is no such thing as a "shell php" unless the maintainer of the site actually built the php cgi vs the php module. AFAIK, most people build the php module because it is more efficient. If this is the case for this guy, then there basicly is no such thing as a "shell php" script. Therefore, in order for this person to attain his goal using php he'd have to write the php script then cron a lynx call. Someone mentioned that this is trivial, however, I disagree simply because look at the number of different processes get called...
"shell php"
init -> crond -> lynx -> apache -> php mod -> php script
perl
init -> crond -> perl -> perl script
Just that alone should be obvious which one is more resource intensive. Without getting into the innerworkings of apache/php/perl etc, it would seem to me that one should go the less resource intensive route no matter how miniscule the amount of extra resources maybe. Don't get me wrong...I really am just sharing my opinion. Im not saying there is a wrong way and a right way Im only sharing the more logical way I see it.