Answer
No, it is not necessary to store the Dynamic Value table in the same geodatabase as the rest of the data; the table can be stored in a different geodatabase. The Attribute Assistant searches within the map document (MXD) to find the Dynamic Value table. It is not necessary for this table to be in the same geodatabase as the feature class or updated, stand-alone table; the Dynamic Value table functions in the current MXD.