Data replication in MS Sql Server 2014 or MS Sync Framework? What is more suitable for my task?

Question

SQL

Hello. I will try to describe everything using the metaphor of the publisher, just like in the Microsoft documentation , in order to more or less speak the same language with you.
I'm reading the information on this whole case, and it looks like there's a lot more to read... The question arises. If on the publisher side (the source of replicated data) tables are created every day under a new name, that is, the Partitioned View mechanism is used, since the data flow for the record is huge, and you need to store records only for a certain period, which means that you have to delete them, then you had to do partitioning into tables, because this way you can very quickly delete entire tables from the database at once without bringing the server to its knees. This is all necessary and there is no getting away from it. Everything is already written.
The question arises:
1. Is it possible to set up database replication so that, for example, when reading data at the publisher from different daily tables (TABLE_NAME1_YYYY_MM_DD), I save this data at the subscriber into one table (TABLE_NAME1). That is, is it possible to configure the system so that it understands that you need to select data from the TABLE_NAME1_2016_03_01 table until it runs out there, and then from TABLE_NAME1_2016_03_02 and write all this data to one table TABLE_NAME1?
2. In my case, which replication is more suitable? As I understand it, transactional replication is not an option here at all. For the data is also deleted at the publisher, and this data must be stored in the archive (subscriber).
3. Haven't read it yet, about MS Sync Frameworkand therefore I will ask, is it not this technology that I need to use? Since there are suspicions that it is not so easy to set up what I described in question 1.