Yes and no

I'll start with "no". USD treats invisibility as a pruning operation, so if
/root/world/truckis flagged as invisible, then it won't even look at anything under it (i.e.,
/root/world/truck/geo/alwaysShowMePrettyPleasemight as well not even exist). So as far as attributes go, it really is only "invisible" or "inherit".
But now "yes". Let's say you have this:
/root
/world
/truck - INVISIBLE
/ geo1
/ geo2
/ geo3 - WANT TO MAKE THIS VISIBLE
The invisibility can be shuffled downwards like this:
/root
/world
/truck
/ geo1 - INVISIBLE
/ geo2 - INVISIBLE
/ geo3
This functionality is provided in
UsdGeomImageable::MakeVisible()(
https://graphics.pixar.com/usd/docs/api/class_usd_geom_imageable.html#af47f609f24c8023ddacc6d216eaef0f3)
I don't currently have strong opinions on if/how this could/should be exposed to users (other than I do think it's a bit strange as a new user that you can't flag a primitive as visible), but you can definitely run this via a Python LOP.