These rows are from the control file and are deleted only when space for this section (AL) is needed (or when the control file is recreated).

There is no harm to have these rows.
What is your actual problem?

Can you remove the archivelogs from the RMAN repository?

DELETE FORCE ARCHIVE LOG....

or perhaps

DELETE FORCE FOREIGN ARCHIVELOG...

should do it.

SQL> select thread#, max(sequence#) from v$archived_log group by thread# order by thread#;

   THREAD# MAX(SEQUENCE#)
---------- --------------
         1        1445213
         2        2665222

Your output gives AL that are already applied, I don't see why your standby db is trying to fetch them.

Post the result of the following statements executed on the standby database (using SQL*Plus):

col inst_id format 999 heading INST
select inst_id, thread#, low_sequence#, high_sequence# 
from gv$archive_gap
order by inst_id, thread#
/
Set lines 125
Col timest     format a14 heading TIMESTAMP
Col message    format a90 trunc
Col severity   format a07 trunc
Col facility   format a03
Select inst_id, to_char(timestamp, 'DD/MM HH24:MI:SS') timest, 
       decode(facility, 
              'Crash Recovery',           'CR',
              'Data Guard',               'DG',
              'Fetch Archive Log',        'FAL',
              'Log Apply Services',       'LAS',
              'Log Transport Services',   'LTS',
              'Network Services',         'NS',
              'Remote File Server',       'RFS',
              'Role Management Services', 'RMS',
                                          substr(facility,1,3)
             ) facility,
        message, severity
from gv$dataguard_status
where severity >= 3 and timestamp >= trunc(sysdate)
order by inst_id, timestamp
/

Don't forget to format your output as explained in How to use [code] tags and make your code easier to read.