the answer was below from the above BOL:
At run time, the Fuzzy Lookup transformation creates temporary
objects, such as tables and indexes, in the SQL Server database that
the transformation connects to. The size of these temporary tables and
indexes is proportionate to the number of rows and tokens in the
reference table and the number of tokens that the Fuzzy Lookup
transformation creates; therefore, they could potentially consume a
significant amount of disk space.
This implies that if we select warm caches the temporary tables create are loading into the SSIS memory space similar to a fully cached lookup transform
The warm cache setting can be foun in the properties tab in bids:

"Pretty Sneaky SSIS"