Executing DMV catalog query after a SSAS cube process forces execution of all DB scripts

Question

After processing an 2012 SSAS cube, then executing a DMV query, such as:

select * from $system.mdschema_sets where [cube_name]='cube name' 

i see in sql profiler it executes scripts of ALL cubes in the database, disregarding the restriction in the query. As my customer's database has many cubes, this operation takes more than 20 secs.

Any idea why this happens?