According to cppreference.com, reinterpret_cast:
Converts between types by reinterpreting the underlying bit pattern.
Mainly the restrictions on reinterpret_cast (not fully captured by the cppreference site) are because of
For a hypothetical reinterpret_cast to number value, different sizes can easily be handled by truncation or zero-extension, since one is into dangerous bit-level territory anyway, so that's not an issue.
By using memcpy or copy_n you work around the alignment issues, but you are still possible victim of trap representations. That means that use of the resulting value might blow up. On some platforms, for some values.
Note that the standard's guarantees about anything, can be and usually are extended by any particular compiler.
Often it can be a good idea to aim for just a little less portability than what you can have by relying solely on the standard.
For example, things get complicated fast when you can't assume that a byte is 8 bits. Making this assumption reduces portability. But still the set of supported platforms is large.