When impoting a database which has wp_options and another _options with another table prefix, Local will take the infos from the first one.
Import a site with a wp_options table and another wpprefix_options table.
The latter being of course the good one.
WordPress will be configured with options found in wp_options and nothing will work of course.
I suppose the previous dev installed another copy of WP but kept the previous tables.
As precisely as you can, list the steps it takes to reliably reproduce the issue.
As no error (and really nothing) is displayed, logged, it took me a while to find this.
Local should at least display a warning and tell the user to clean its DB.
I recognize it’s the first time I see this.