In fact, you can use any db for different usecases, but there are ups and downs:
influxdb: you will have to learn how to use, (yes, there is a windows version), database is growing, you have to maintain (if not purging old data via configuration), only few tools for using the data outside influxdb.
(my)sql (or something similar): even more complex than influxdb, although... maybe you already have an installation and can just use it database is growing and you have to maintain, but there are way more tools to use data, sql is very common, so maybe you could even produce your own tool if needed.
rrd4j: database is not growing, but the data is the less precise, the older the data is, you can only store numbers, no strings, no dates, no time, no boolean (but openhab does boolean as 1 and 0).
mapdb: only the last state is persisted, so no historical data.
So, if you want to persist every item just to restoreOnStartup, mapdb would perfectly fit. If you only want a bunch of items to restoreOnStartup (and they are already persisted in another database), there is no need for mapdb.
If you want graphs and do not have much space for data, don't want to think about maintaining, use rrd4j.
If the default graphs do not fit (poor graphic quality...) you would have to use grafana,which fits perfectly to influxdb.
If you need very precise data over years and years, or string data to be persisted, you will have to use a sql-like-database.