Do you need to include all foreing keys of a parent table in the child table?
I think I follow but here's an example using more meaningful names:

Given these two tables:

CREATE TABLE Persons 
(
 person_ID INTEGER NOT NULL UNIQUE
);

CREATE TABLE Employees 
(
 employee_ID INTEGER NOT NULL UNIQUE, 
 person_ID INTEGER NOT NULL UNIQUE, 
 FOREIGN KEY (person_ID)
    REFERENCES Persons (person_ID), 
);


I think you are saying you would add a referencing table like this:

CREATE TABLE HourlyPaidEmployees
(
 employee_ID INTEGER NOT NULL UNIQUE, 
 FOREIGN KEY (employee_ID)
    REFERENCES Employees (employee_ID) 
);


I would be inclined to agree because I am a human who can understand that given two candidate keys I will choose employee_ID because the table name HourlyPaidEmployees strongly suggests it pertains to employees.

However, it seems your software generates this:

CREATE TABLE HourlyPaidEmployees
(
 employee_ID INTEGER NOT NULL UNIQUE, 
 FOREIGN KEY (employee_ID)
    REFERENCES Employees (employee_ID),
 person_ID INTEGER NOT NULL UNIQUE, 
 FOREIGN KEY (person_ID)
    REFERENCES Employees (person_ID) 
);


I would guess that the software has been designed so that given two candidate keys it should not attempt to 'guess' which one to use and therefore uses both and leaves it to the user to decide which one to remove.