Part 1 of the answer to your question is no, you can't selectively tell MySQL what not to store in the InnoDB buffer pool. It's an integral part of how InnoDB manipulates table data.
Part 2 is that you don't really want to or need to, because it's smart enough to work out what should stay there if the pool is not large enough to retain your entire data set.
Incidentally, I might have mentioned previously... don't trust tuning scripts.
At best, they may give you "interesting things" to investigate and read up on, but it's absolutely impossible to properly "tune" a MySQL server without understanding the nature of the data that's on that server... and, you're just as likely to tweak your performance downward as well as up.
InnoDB doesn't load anything into the buffer pool that isn't in some way useful. Leave a newly-restarted MySQL server alone without running any queries, and the buffer pool will sit there, allocated but mostly empty.
SELECT from a table, and some number of the pages from that table's tablespace on disk will be loaded into the pool, but not usually all of them. Which pages depends on which rows you retrieve, what indexes are needed to find them, whether it's doing read-ahead, etc.
UPDATE a table and the pages with the rows you update will be loaded into the pool, modified in the pool, and then written back to disk in the background.
DELETE bring pages into the pool and ultimately flush them back to disk also.
But InnoDB keeps track of how "useful" what's currently in the buffer pool is, how recently it was needed, whether any changes have already been written back to disk or not, and will evict pages to make room for other pages when the pool is full. Many of my production servers have an InnoDB buffer pool that is smaller than the server's data set and essentially 100% full 100% of the time, but there's no performance impact from that when a large amount of the data hasn't been accessed for some time.
If a page in the pool hasn't been changed since it was loaded, or if it has been changed but since that time the changes have been written back to disk, and it hasn't been needed for a while, that chunk of the pool is readily reusable for something else the next time InnoDB wants to load something back into the pool from disk... so it's "in use" but still "available."
Unless you're frequently accessing all 50GB of those blobs, the size recommendation from the tuning script is overblown. Of course, in an ideal world, your pool would be larger than all of your tables and indexes and you'd have an all-in-memory database that only had to access the disk to flush changes out... but in the real world of real data, the chances are pretty good that a large portion of your data is not frequently accessed, and there's no way for a simple script to anticipate those conditions.