Managed Software Updates with Blueprints

Wait so I’m confused. Whats the ask?  

It seems the blueprints are doing exactly what they are meant to do according to your screenshots. BSIs aren’t available to be set via MDM configuration profiles, only RSRs (which I recently learned from an Apple rep are not the same thing). 
 

I would have assumed that if I neither enable nor disable it in another blueprint, it would simply be ignored.
We basically have 3 different statuses. enabled, disabled and not set. but in the mdm profile on the mac it appears as enabled if i did not set it.
does that make sense? i don't get it.

Ah yes. So unset takes the default configuration that Apple sets. If you have a declaration set though, it’ll respect that over anything/everyhing else. 

Hopefully I’m understanding you correctly and providing decent information. 

I have run into similar before, you have to be specific.
If you do not want it Enabled, then Disable it.
I think you will find not setting something should allow the end user the choice to set or not, and will show up as whatever the Apple Default setting is.
I say should there because I have worked in the world of Apple long enough to know that their world and the rest of the world are not the same.

Okay, and what happens if it is configured as “Disabled” in one blueprint but left “Not Configured” in another blueprint? Will the more restrictive setting take precedence?

I’m trying to take the approach of blocks and predicates. I started out with multiple blueprints for updates and it rapidly became unruly.

I believe it follows the same as profiles so the more restrictive setting takes precedence.

It’s supposed to.  Most restrictive is supposed to take precedence.

If its 2 Blueprints on the same device, the theory is Most restrictive will apply.