that the user can save at profile edit without the need to fill in all required fields
That completely contradicts the point of the fields being required. Set them to not be required.
Or the group fields has a placeholder also in the profile edit, so start and not shown with all fields of the first set in the profile edit.
That would just confuse the users as to what the field even does. There are no plans for this.
The best I can suggest for your required, but not required, use case is to use CB Conditional to show/hide the entire field group only when it's relevant. This would circumvent the required state while hidden.