Prevent records from a scoped table being captured in Application

I have a table in a scoped application that extends 'Scheduled Script'.

For some reason, all record create/updates for that table are being captured in the Update Set (not talking about configuration, but record creation).

This is especially strange because the Scheduled Script table is normally not captured in Update Sets and I did not set this table up to be captured in Update Sets,

The new/updated records for this table are not being captured in any Update Sets, yet they continue to be added as an Application File with every record update.

That being said, the 'track in Update Sets' UI Action is not available.

No parent tables in the hierarchy are set to capture in Update Sets.

I have also added the 'update_sync=false' attribute.

Is there any way to stop this from happening?

I think I need to stop this table from extending sys_metadata but unsure how to do this and how this happened in the first place.