"I would never use I2C EEPROM like RAM."

Yes, I agree - but that wasn't my point (I didn't specifically mention EEPROM).

"two functions (block read and write) are used to update the RAM or the EEPROM."

My idea was that, by cunning use of the Keil far memory type, your 'C' source code need know nothing about the functions and can just use normal assignments.
Of course, as you say, the programmer would still have to bear in mind the type of the underlying hardware, and treat it accordingly.

From Jon's reply to my cross-post on the Keil forum, it would seem that this is indeed possible:
http://www.keil.com/discuss/docs/thread1754.htm

(His reply also conatains a useful explanation of the way Keil handles all the different memory spaces)