SAP Replication Server does not immediately apply here, though some of its features could potentially be used for this kind of scenario.
First, I've seen somewhat similar requirements before in Swiss banks, where data about Swiss bank account holders could only be viewed by bank employees located on Swiss soil (i.e. the DBAs in the IT department of that bank's office in, say, London, would nto have access top such data).
A long story short: this could be implemented with SAP ASE, using the column encryption features in SAP ASE. (there is more to it, it's too big a story to detail the design here).
As far as Replication Server is concerned, it will just replicate data, whether encrypted or not. The trick is to make sure it can be decrypted by the right users at the various replicate sites.
Ignoring ASE, how RepServer may help in cases like these is by using functions trings that control what happens when data is replicated into aa particular remote site. For example, it can mask certain columns, or it can perform additional updates on other tables. This requires designing the data model in such a way that it is clear where a data row originated, in terms of the problem here: does this row originate from a Russian server or from outside? Typically this takes the shape of an additional column in the replicated table with an ID of the primary site where the row was created. See the Replication Server 'Design Guide' manual for examples.
Bottom line: it may be possible to do this, but it will likely require a properly designed data model that takes these requirements into account. It does not sound like a simple problem to solve, but that due to the requirements rather than the capabilities of RepServer.