By default, if you (say)
- restore files for SYSTEM...etc but not ARCHIVE_MESSAGES from (say) Oct 1
- restore files for ARCHIVE_MESSAGES from (say) June 1
then the database will want archive logs from June 1 onwards to bring all files back into sync, because we need to roll forward all files to a common point in time. That is one option.
Another option is if the ARCHIVE_MESSAGES can be made read only ( I don't know your usage). Once a tablespace is read only, a single backup taken after the point can be used continuously as long as the tablespace is not made read write again.
We do also support tablespace point in time recovery, so you could restore ARCHIVE_MESSAGES from June and *leave* it at the June timeframe whilst the rest of the system is at October. There's a number of restrictions here. See
https://docs.oracle.com/en/database/oracle/oracle-database/21/bradv/performing-rman-tspitr.html#GUID-40A9A54A-8742-42D9-AB47-F0B61439A100 for details