Answer
Yes, that pattern continues to work across current releases — just make sure the custom component is declared in the solution set's custom-components configuration and that any modifications correctly declare their real component dependencies, since missing or incorrect dependency declarations (not the separate-component approach itself) are what typically cause deployment errors.