Feature request: Backup copy job with a different block size than the source job

[petesteven]

Most of my customers write their primary backups to a hardened repository with a default block size of 1MB.
Unfortunately, the block size of the source job is also used for the backup copy. This is not a problem when backing up to a second hardened repository. More and more customers are using S3 in the cloud or on-premises as their backup copy target.
With S3, I should set the block size to 4 or 8MB due to API costs and the number of objects (I have 84,000,000 S3 objects with 60 days of retention on an SQL Server for one customer. We are having massive problems with S3 here).
It would be good if the block size in the backup copy job could be selected separately from the primary backup job.