From the current Standard draft ([basic.types.general]/2):
For any object (other than a potentially-overlapping subobject) of trivially copyable type
T
, whether or not the object holds a valid value of typeT
, the underlying bytes ([intro.memory]) making up the object can be copied into an array ofchar
,unsigned char
, orstd::byte
([cstddef.syn]).
If the content of that array is copied back into the object, the object shall subsequently hold its original value.
So yes, the same aliasing rules apply for the three types, just as cppreference sums up.
It also might be valuable to mention ([basic.lval]/11):
If a program attempts to access the stored value of an object through a glvalue whose type is not similar to one of the following types the behavior is undefined: 44
- […]
- a
char
,unsigned char
, orstd::byte
type.
44 The intent of this list is to specify those circumstances in which an object can or cannot be aliased.