Replication consistently fails to bring new rows to subscriber
I believe you are running into the issue described in Subqueries that you define on merge articles are not re-evaluated.

From the article the cause is:


  This behavior occurs because the query is not re-evaluated and the row
  is not propagated as part of replication when you update a row in a
  table that is referenced by a subquery. Although you can place a
  subquery in a row filter, it is not a join filter. Although you can
  define a subquery that is based on data from another table, this too
  can cause unexpected results at the Subscriber.


And the resolution is:


  To resolve this behavior, use a join filter when you want the filter
  definition to be re-evaluated during every merge synchronization
  process.