The `OBJECTPROPERTY` call requires a schema stability (Sch-S) lock, which is only [incompatible][1] with a schema modification (Sch-M) lock.

The `BULK INSERT` will take a Sch-M lock in some circumstances. These are listed in the "Table Locking and Logging During Bulk Import" section of [Guidelines for Optimizing Bulk Import][2] in Books Online:

![Bulk Import Locking][3]

If the destination table is clustered, you may find enabling [trace flag 610][4] helps. Please read the whole series of those posts and the [Data Loading Performance Guide][5] and test thoroughly if you decide to go this route.

I have no idea why SSDT checks the `IsEncrypted` property for tables. I cannot imagine a scenario where that makes sense, but that's a question for the SSDT people.

  [1]: https://technet.microsoft.com/en-us/library/ms186396.aspx
  [2]: https://msdn.microsoft.com/en-us/library/ms177445.aspx
  [3]: https://i.sstatic.net/Y08bh.png
  [4]: http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/03/23/minimal-logging-changes-in-sql-server-2008-part-2.aspx
  [5]: https://msdn.microsoft.com/en-us/library/dd425070.aspx