Sorry to hear this is giving you trouble – each of the data types supported by this custom module could be a little different, but I think if you were to peek in the /includes/{type}.php code for the particular data type you’re loading, you can see how it goes through search and/or exclude_search, that’s really where all the filtering logic gets applied. Glancing at an older version of that code that I’m not sure if it matches what you’re using, I wonder if there’s some way of using the _mode setting to get the overlap you’re after? Something like exclude_search_mode=all ?
well, I couldn’t get it to work when there is also a search argument, but I figured out a way to hide what I needed to with css, so I’m peaceful about it for now…