Caching subscription ids in minimongo to vastly simplify client-side querying

Adding a special field to documents at publish time is a known hack to help in fixing the painful limitations of Meteor publish mechanism.

Those limitations are somewhat acknowledged by MDG here (other examples here and here).

However, in your case, I don’t understand what you’re trying to achieve.
Also, what is getSubId()? Does it relate to the subscriptionId fields of subscription handles?