Memory usage optimization of the broadcasting mapping rule strategy

## Background
Currently, a mapping table is fetched, broadcasted and left in memory for each instance of the usage of the mapping table. Clearly, there should be a way to keep only one instance on a mapping table in memory when the same mapping table is used more than once.

## Feature
Improve broadcasting strategy's memory usage by adding logic for keeping mapping tables in memory only once.