As long as you can use any port if not specified in platformio.ini, when you diag wrong port, why not offer to use the available one?

What kind of issue is this?
suggestion

• Question.
  This issue tracker is not the place for questions. If you want to ask how to do something,
  or to understand why something isn't working the way you expect it to,
  use Community Forums or Premium Support

• PlatformIO IDE.
  All issues related to PlatformIO IDE should be reported to the
  PlatformIO IDE for VSCode repository

• Development Platform or Board.
  All issues (building, uploading, adding new boards, etc.) related to PlatformIO development platforms
  should be reported to appropriate repository related to your hardware
  https://github.com/topics/platformio-platform

• Feature Request.
  Start by telling us what problem you’re trying to solve. Often a solution
  already exists! Don’t send pull requests to implement new features without first getting our
  support. Sometimes we leave features out on purpose to keep the project small.

• PlatformIO Core.
  If you’ve found a bug, please provide an information below.

You can erase any parts of this template not applicable to your Issue.

Configuration

Operating system:

PlatformIO Version (platformio --version):

Description of problem

Steps to Reproduce

Actual Results

Expected Results

If problems with PlatformIO Build System:

The content of platformio.ini:

Insert here...

Source file to reproduce issue:

Insert here...

Additional info

The issue does not name a file, test, command, operating system, or reproducible configuration. Start by tracing PlatformIO Core's upload or port-diagnostic CLI flow and how available ports are discovered; define done as offering a detected alternative when the configured port is invalid, with tests covering the selection behavior.