Probably. It's hard to predict how language design decisions will impact performance (and everything else, such as ease of use and productivity). That's why it's good to have an iterative process (like Swift is now adopting) instead of being rigid, inflexible, and opinionated.
A post last week featured Lattner writing about Swift treating methods as final when they weren't declared that way (https://lists.swift.org/pipermail/swift-evolution/Week-of-Mo...). I wonder if the early thought was that they'd get enough mileage out of those "cheats", and then later decided that final should be the default.