If I understand you correctly you have another database you want WeeWX to connect to. This database does not have a dateTime field that stores a Unix epoch timestamp, but rather it has a field that stores a UTC date-time in a YYYY-mm-dd HH:MM:SS format. The database does not have usUnits or interval fields. I assume you wish to be able to (as a minimum) use data from this database in WeeWX generated reports.
WeeWX will certainly be able to 'connect' to the database but unless you have a dateTime field that stores a Unix epoch timestamp you will be severely limited in what WeeWX can do with the data in the database. The reason being that almost all WeeWX report tags (eg $current, $day, $week etc) rely on there being a dateTime field (that holds a Unix epoch timestamp) that WeeWX can use in the underlying SQL queries that support the WeeWX tags. The lack of a usUnits field will certainly create issues with units whether you are converting units or not. The lack of an interval field is probably less of an issue but it will certainly create some limitations as well.
Your best approach might be to develop a WeeWX service that reads the relevant data from the external database, makes the necessary conversion from the UTC date-time field and determines a usUnits value and the saves these fields and the relevant data in a suitable WeeWX database. If the system that produces the external database has some means on interrogating it for the data you are interested in, and if your WeeWX machine can connect to it, another approach maybe to develop a WeeWX service to obtain the data of interest direct from the external system and save it to a WeeWX database. Ether way will take some effort, the first approach will require some SQL skills and the second, if possible, some basic skills like used in many of the WeeWX drivers.
Gary