WordPress will only do a database lookup the first time if the option hasn’t been auto-loaded or already accessed prior. The performance hit is negligible, however if you’re loading multiple separate options with a bunch of get_options instead of using the serialised option functionality, then the initial lookup * X number of separate option rows could potentially cause performance issues.
In your other question which is a duplicate of this one, I answer the question with an example of best practice code if you’re concerned with get_option performance here.