I've tried to reproduce this bug on Satellite 6.3.3, and the content host is properly updated when the content view or lifecycle environment is changed, and the Host::Update task is properly run. This BZ appears to be fixed in 6.3.3.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:2915