ID 538577 - GeoImport nodes with Alembic files don't pass {lastmodified} data downstream

Problem summary:
GeoImport nodes with Alembic files don't pass {lastmodified} data downstream.
 
This issue does not seem to affect .usd/usda files.
 
Customer reported version:
Nuke 14.0v3
 
Customer reported platform:
CentOS 7
 
Steps to reproduce:
1) Open Nuke and create a GeoImport node in the Node Graph.
2) Select an Alembic (.abc) file to import.
3) Create a GeoTransform node and press the "1" key to View it.
4) Observe how the Mask reports that there are no matched paths with {lastmodified}:

 
Expected behavior:
GeoImport nodes should have some data available in {lastmodified} when importing Alembic files.
 
Actual behavior:
No {lastmodified} information is passed downstream from the GeoImport node, resulting in the GeoTransform node not affecting any geometry:

Additionally, error messages such as Error: Alembic file Set() not supported or Error: Failed verification: ' primInfo ' may be printed to the Terminal:

 
Workaround:
There is no known workaround for {lastmodified} at this time, but a different mask, such as /*, could be specified:

 
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, CentOS 7
Nuke 14.0v2 - Windows 10
Nuke 14.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 14.0v1 - This feature (the GeoImport node) did not exist before this version.