On iOS, if a superview's userInteractionEnabled is NO, then all subviews are disabled as well?

You can override hitTest(_:withEvent:) to ignore the view itself, but still deliver touches to its subviews.

class ContainerStackView : UIStackView {
    override func hitTest(_ point: CGPoint, with event: UIEvent?) -> UIView? {
        let result = super.hitTest(point, with: event)
        if result == self { return nil }
        return result
    }
}

If this may be helpful, I found this in Programming iOS 5 by Matt Neuburg, p. 467:

userInteractionEnabled

If set to NO, this view (along with its subviews) is excluded from receiving touches. Touches on this view or one of its subviews "fall through" to a view behind it.

Further more, Apple's Event Handling Guide for iOS says:

The window object uses hit-testing and the responder chain to find the view to receive the touch event. In hit-testing, a window calls hitTest:withEvent: on the top-most view of the view hierarchy; this method proceeds by recursively calling pointInside:withEvent: on each view in the view hierarchy that returns YES, proceeding down the hierarchy until it finds the subview within whose bounds the touch took place. That view becomes the hit-test view.

and Programming iOS 5 by Matt Neuburg, p.485 mentioned that if a view is marked userInteractionEnabled as NO, or hidden as YES, or opacity is close to 0, then the view and its subview will not be traversed by HitTest (and therefore not considered for any touch).

Updated: I suppose it also works this way if we think about parent-child situation in other scenario. For example, in HTML, if there is a div and there are children all under this div, and now this div is set to display: none, then it makes sense that all the children are not displayed as well. So if a parent is set to not interact with the user, it also makes sense that the children do not interact with the user as well.

You can't do that,

Instead you would change the arrangment of your views like following:

Main View -> subViews

To

Container View -> Main View that you want to set as inactive
               -> other views that you want to still be active

So your current main view and you current subviews will become siblings, children of a new container view