I haven't tried or tested any of this but at first glance I don't see why you couldn't. If that paper isn't completely out of date.
I don't know if you missed this but this seems to be the most important part here:
So the only problem you face is knowing the client id, which you seem to already have, and the other seemingly random number that comes right before the hex string. I would think you could brute force that number, it seems to fall within a 1024 or less number range.* update (courtesy John Jacob): The hex string is created using "md5sum [file_name] | cut -c3-16". It can also be replaced by a cache time-to -live value like "1d" for one day, and "15m" for 15 mins.
Why would you specifically need akamai's cache wouldn't there be others that you could use?
Anyways, hope this helped and good luck!