Hey yes, Relatr implemented TA in its latest version. It allow users to set a relatr instance in their 10040 event and also “activate” a instance so it refreshes their ranks periodically. In the other hand the way relatr publishes 30382 events for other users, even the ones that haven't touched or know about relatr, its in a “lazy” way, which means that the ranks it publishes are triggered lazily by the request it receives when anyone uses it’s endpoints, so it’s something either triggered by an user willing to use a instance of relatr as TA provider or either organically and in a lazy way when anyone uses it to search or to rank pubkeys. 

The rationale behind this is to reduce the fan out pressure of publishing loads of events and the storage pressure in relays that store these events. The result was that it started slowly and then in a short amount of time loads of npubs had their scores published by the public relatr instance we are running at nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.

In the other hand, can you explain what do you mean in your last paragraph? I want to answer, but im not sure what do you mean, CVM is a protocol that allows communications between client an services in a permissionless, private, and structured way, where the service can run easily in a closet and users can switch between providers.