Performance hit for marking a Swift struct method as mutating?

Just curious: It this somehow related to Fastest way to get (const) pointer to struct for inter-operability with C/C++, where it was observed that withUnsafePointer(to: someInstanceVariable) makes a copy, whereas withUnsafePointer(to: &someInstanceVariable) avoids the copy?