I use areca to backup a few file servers to a central one. Then, from the server itself, I open the configuration files on the backup to check them, see history and sometimes to restore an individual file.
I have either to let the backup serer open network connections to itself, or to hand edit a copy of the configuration files so they appear to be local ones. Not so hard. but also not so easy for the junior sysadmins.
Areca could detect, when it knows it's opening a backup configuration, that the archives themselves are local (say, if its opening from an areca_config_backup folder, see if there is a storage_XXXXX folder at the same level, with archive files). Then create on-the-fly a configuration acessing those files as local, thus not needing networking overhead.