Not sure this is possible, why are you doing this? To identify framework related hotfixes (normally installed by import directly)? Eventually we are going to make all hotfixes unified, including frameworks, but we are not there yet.
Irrespective of whether it is a DL item or HFIX jar containing rule changes , it should ideally be stored in the ServiceExport directory on the server.
So that should be one quick way to check whether you have uploaded the framework HFIX es into system.
Also, you can try importing the HFIX again by checking " Enable advanced mode to provide more granular control over the import process" so that at runtime you can see the name of the rules which system wants to import to system.
At this point, if you see a message which says " Instances already loaded " then you can assume that the particular HFIX is already loaded.
I would suggest examining instances of the Log-PegaRULESMove class in the system.
as per the Help documentation, "Log-PegaRULESMove concrete class contains one instance for each execution of the Import Archive and Export Archive tools. Properties in each instance identify the date and time the execution started, which user ran the tool, a record count, and the name of the ZIP file used. "
From this you should be able to identify any archive that has been imported to the system (including hot fixes not added via Update Manager) using the Import (or Export) facility.