No further problems reported. Closing as fixed.

There is a very minor inconsistency in the ID used for the "time stamp on file X is in the future" warning between the interpreter and dynamic library functions.

libinterp/parse-tree/oct-parse.yy

  warning_with_id ("Octave:future-time-stamp",
                   "time stamp for '%s' is in the future", nm.c_str ())

liboctave/util/oct-shlib.cc

    (*current_liboctave_warning_with_id_handler)
      ("Octave:warn-future-time-stamp",
       "timestamp on file %s is in the future", m_file.c_str ());

These are the same check, just done in different contexts, so my expectation is they should both use the same warning ID. Given the standard naming scheme, that would be Octave:future-time-stamp.

Thus the fix would be to change oct-shlib.cc to use that. I will attach a patch doing so.